[SERVER-46069] Use invalidateShardForShardedCollection in the router's moveChunk command Created: 10/Feb/20  Updated: 29/Oct/23  Resolved: 11/Feb/20

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

Type: Bug Priority: Major - P3
Reporter: Blake Oler Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-02-24
Participants:

 Description   

We try to move the routingInfo twice in the router's moveChunk command. This is invariably a bug. We don't need to go through the onStaleShardVersion() path in order to invalidate this collection – we can use invalidateShardForShardedCollection() in order to achieve the same result, which is marking the shard as stale.



 Comments   
Comment by Githook User [ 11/Feb/20 ]

Author:

{'name': 'Blake Oler', 'username': 'BlakeIsBlake', 'email': 'blake.oler@mongodb.com'}

Message: SERVER-46069 Use invalidateShardForShardedCollection in the router's moveChunk command
Branch: master
https://github.com/mongodb/mongo/commit/0e593aa4ea3cc742fef12cf78b479898898756b7

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