-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
Storage Execution 2025-08-04, Repl 2025-09-01, Repl 2025-09-15
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When the intent registration feature flag is enabled, we do not take the RSTL lock when attempting to abort a two phase index build. This means that it's possible for the node issuing the abort index build command to be a writable primary here, but then have been forced to step down by the time we check this invariant.
Since the index build coordinator thread marks itself unkillable here, the step down also cannot interrupt the command.
One way to get around this could be to use BlockingWrite intent when trying to abort a two phase index build
- related to
-
SERVER-109256 Difficult to know which intent to use on shared primary + secondary code paths
-
- Open
-
-
SERVER-110060 Add guardrail to detect new oplog entries being written by secondary
-
- Needs Scheduling
-