Since after SERVER-60336 _configsvrMoveChunk runs the code that send the commands to the shards in a different thread client than the command and then joins it, the original command thread is not made aware of the operationTime returned from the shards, and thus it does not gossip it back to the router.
To fix it, after joining the thread, the original command thread must set its lastOpTime to the system's lastOpTime
- causes
-
SERVER-61742 Balancer may trip invariants due to concurrent usage of opCtx from different threads
-
- Closed
-
- is caused by
-
SERVER-60336 Remove the MigrationScheduler component from the Balancer (and replace it with BalancerCommandsScheduler)
-
- Closed
-