-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.3.10
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 18 (08/05/16)
-
0
There is a race in the new initial sync code where Fetcher::cancel() can be called while we're in a previous batch's _callback() but before the next batch is scheduled. This means that Fetcher::cancel() is called when the callback handle is invalid, and thus Fetcher::_inShutdown is never set to true. The next batch is then scheduled and _inShutdown is never set to false.
- related to
-
SERVER-25913 hold mutex while scheduling getmore request in Fetcher
- Closed