[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 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: |
| Comment by Githook User [ 22/Dec/19 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: No functional changes. |