Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.0.1
-
None
-
Untriaged
-
Unknown
Description
In https://issues.couchbase.com/browse/CBSE-6518, we noticed that when indexes on MAINT_STREAM are dropped before indexes on INIT_STREAM during rebalance, new index builds remain stuck. The num_docs_indexes is being shown as "0" but the build progress shows 100% and it does not change. The issue can be reproduced locally using the following steps:
- Set up a 2 node cluster - 1KV+n1ql,1index
- Populate 10M docs into "default" bucket
- Create and build an index idx_1
- After index idx_1 is built, start building another index idx_2
- When idx_2 is building, rebalance-in a KV node
- While the rebalance is happening and idx_2 is building, drop idx_1 first and then idx_2
- After rebalance finishes, create and build a new index idx_3
- The index build for idx_3 remains stuck at 100% and the num_docs_indexed would be "0"
Attachments
Issue Links
- is a backport of
-
MB-33392 Index builds remains stuck when indexes on MAINT_STREAM are dropped before indexes on INIT_STREAM during rebalance
- Closed