[SERVER-44855] Investigate ShardRegistry reload on config server during removeShard Created: 26/Nov/19  Updated: 29/Oct/23  Resolved: 22/Dec/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.3.2
Fix Version/s: 4.3.3

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Kaloian Manassiev
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 2019-12-02, Sharding 2019-12-16, Sharding 2019-12-30
Participants:

 Description   

Currently, ShardRegistry gets reloaded in the config server while running removeShard:

https://github.com/mongodb/mongo/blob/ec9a2f13d82f141d8aca9e3df9e9112b722f2563/src/mongo/db/s/config/sharding_catalog_manager_shard_operations.cpp#L810
https://github.com/mongodb/mongo/blob/ec9a2f13d82f141d8aca9e3df9e9112b722f2563/src/mongo/db/s/config/sharding_catalog_manager_shard_operations.cpp#L852

However, the reload is done with read concern majority so it might not see the changes that were applied during the removeShard command. Investigate whether if reload is even needed in the config server and if yes, how to fix it.



 Comments   
Comment by Githook User [ 22/Dec/19 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-44855 Remove unused code from removeShard and ShardingTest
Branch: master
https://github.com/mongodb/mongo/commit/d6cc8fa5d0319c470e12887836498d3f2f288c29

Comment by Githook User [ 22/Dec/19 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-44855 Add comments and cleanup the catalog manager

No functional changes.
Branch: master
https://github.com/mongodb/mongo/commit/8add28c5da7d9906aa3625fce074612f634e1619

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