-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Server Programmability
-
ALL
The failCommand failpoint accepts a blockTimeMS argument which causes the affected command to block. However, while performing this blocking, the lock associated with the failCommand failpoint is held, so if another connection tries to disable this failpoint, that configureFailPoint command will also block. This should be fixed so that test cleanup can disable a blocking failCommand failpoint without killing the operation.
- related to
-
SERVER-96124 Inconsistency between failpoint nTimes and waitForTimesEntered counters
- Backlog