-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
CAR Team 2026-10-12, CAR Team 2026-10-26, CAR Team 2026-11-09
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
As concluded from BF-46384 it's possible that the if there is a config index being built in progress, it still continues to be building even if the node loses the election and steps down. In such cases, it's possible that it can go through a step up and currently it would lead to attempt to create another config index that would be conflicting with the one that is in progress, which leads to a fatal failure. Ideally instead we should simply skip re-built of such index and wait for existing index build job to complete.
- is duplicated by
-
SERVER-136868 resetPlacementHistory can leave config.placementHistory recreated without its secondary indexes by a concurrent DDL commit, crashing the config server on step-up (fassert 40184)
-
- Closed
-