[SERVER-61113] _configsvrMoveChunk does not gossip the proper operationTime back to the router Created: 29/Oct/21  Updated: 29/Oct/23  Resolved: 15/Nov/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.2.0

Type: Bug Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Paolo Polato
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
causes SERVER-61742 Balancer may trip invariants due to c... Closed
is caused by SERVER-60336 Remove the MigrationScheduler compone... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2021-11-01, Sharding EMEA 2021-11-15, Sharding EMEA 2021-11-29
Participants:
Linked BF Score: 59

 Description   

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



 Comments   
Comment by Githook User [ 15/Nov/21 ]

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-61113 make _configsvrMoveChunk gossip the operationTime back to the router
Branch: master
https://github.com/mongodb/mongo/commit/0cdd5dd4ebf56bd913ee72c6754d6d8649c19a32

Generated at Thu Feb 08 05:51:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.