-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Execution EMEA Team 2023-08-07, Execution EMEA Team 2023-08-21
-
135
Although there are no interrupt points called directly within _completeExternalAbort, some OpObservers might happen to check for interrupts. For instance, this happened during SERVER-69461, which made some sharding acquisitions interruptible and triggered fassert 4656011.
- is depended on by
-
SERVER-69461 The behaviour of lock acquisitions differs depending on whether OpContext or Locker is used
- Closed
- is related to
-
SERVER-48062 Index build abort can race with stepdown
- Closed
-
SERVER-48524 Acquire config.system.indexBuilds lock earlier and with collection lock
- Closed
- related to
-
SERVER-83168 Make index build uninterruptible after commit
- Closed