-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Repl 2020-11-02
-
0
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Using a future-based join()/joinAsync() for AbstractAsyncComponent introduces a subtle race where a subclass may be destroyed while holding the mutex. Since we turned out not to need joinAsync, it is simplest to fix this by reverting to the old condition variable based method.
- is related to
-
SERVER-28204 Recoverable Rollback: Add server parameter to select between 3.4 and 3.6 rollback implementations
-
- Closed
-
-
-
- Closed
-