What I want to call attention to is the amount of disk space that this feature can quickly consume.
Previously, we did not see a need to provide a large amount of disk space to the index location, in the same way that we had for our data buckets. With the introduction of FTS that is no longer the case for us. For example, we ran a full text search on a small sample bucket consisting of just over 200k items and about 1.7 GB on disk. The resulting index quickly consumed 27GB of disk space.
In short, if you intend to leverage FTS in your development environments, I suggest you allocate as much drive space as you can to your index location. We love this feature and are excited about future uses within our platform and applications. I am currently in the process of re-architecting our environment to accommodate the additional overhead. I’ll follow up with more specifics on the environment once we validate.
Reference: Couchbase Full Text Search