-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Execution Team 2019-12-02, Execution Team 2019-12-16
-
20
We replicate the "startIndexBuild" oplog entry on the caller thread, then schedule the index build task on a thread pool. This leads to a deadlock scenario described in SERVER-44250. That ticket will fix the issue with a mutex, but it depends on the internal queuing implementation of the thread pool.
To guarantee index builds are scheduled correctly, we should really replicate the oplog entry on the index build thread, rather than the caller.
- related to
-
SERVER-44250 startIndexBuild oplog write and thread pool scheduling are not serialized between concurrent threads on primaries
-
- Closed
-
-
-
- Closed
-