[SERVER-63905] ConfigureCollectionBalancing command should refresh collection routing info Created: 23/Feb/22  Updated: 29/Oct/23  Resolved: 25/Feb/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0, 5.3.0-rc3

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

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.3
Sprint: Sharding EMEA 2022-03-07
Participants:

 Description   

If a database is dropped and recreated and then configure collection balancing is run immediately, the call to getShardedCollectionRoutingInfo can return a stale uuid for the collection which will cause a uassertion that there is a conflicting operation in progress. The command will retry, but will still get stale information. We should update the call to the catalog cache to use getShardedCollectionRoutingInfoWithRefresh



 Comments   
Comment by Githook User [ 04/Mar/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-63905 ConfigureCollectionBalancing command should refresh collection routing info

(cherry picked from commit f2fca650993b81e6083a51ae411c272074a82c38)
Branch: v5.3
https://github.com/mongodb/mongo/commit/73e2bd2712700cf380b0c7f24ab0e56b80a7edc3

Comment by Githook User [ 25/Feb/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-63905 ConfigureCollectionBalancing command should refresh collection routing info
Branch: master
https://github.com/mongodb/mongo/commit/f2fca650993b81e6083a51ae411c272074a82c38

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