The Global Secondary Index update is always async. When large number of documents are updated, the N1QL query will not be blocked, the query results will show eventual consistency and seem to lag depending upon index backlog.
Will the eventual consistency also apply to query against the FTS index? I have read the Couchbase documentations and it is not clear to me what/when will trigger the FTS index rebuilt. Does this FTS index get rebuilt whenever a single document is added/updated? or there is some kind of smart scheduling, like every 15 mins the FTS indexing service is going to wake up and check whether this is new document update? or whether the FTS indexing service is going to wait for at least 100 documents update then do the index rebuilt. Since our customers may upload lots of documents at once, we are worried whether this is going to significantly slow down the indexing of the FTS index or block the query against the FTS index or cause the full text search against the FTS not perform at all.