Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Fully Compatible
-
ALL
-
Repl 2020-02-10, Repl 2020-02-24
-
0
Description
Similar to SERVER-45934, since DBClientCursor APIs are not thread safe, calling DBClientCursor::more concurrently in two different threads can race in setting private members. In particular, one thread can set cursorId to 0 during dataReceived while the other thread checking the cursorId in more(). Thus, in CurrentOpExhaustCursorTest, runOneGetMore can race with the startExhaustQuery thread on calling more(), resulting in false positive failures.
Attachments
Issue Links
- is related to
-
SERVER-45934 Race in ExhaustCursorUpdatesLastKnownCommittedOpTime integration test
-
- Closed
-