-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Critical - P2
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
ALL
-
v9.0
-
Repl 2026-10-12
-
None
-
None
-
None
-
None
-
None
-
None
-
None
IndexBuildsCoordinator::onStepUp acquires a lock in a loop to make sure we are primary. This loop starts before we are guaranteed to be a writable primary which necessitates the loop. If the stepUp is cancelled then this loop is not able to complete
Subsequent stepups need to wait for the previous stepUp to end from the perspective of the index builds coordinator, which means the node is never able to step up again.