[SERVER-44893] ShardingCatalogManager::removeShard incorrectly assumes that the shard id query will return results Created: 02/Dec/19 Updated: 29/Oct/23 Resolved: 02/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2019-12-02, Sharding 2019-12-16 | ||||
| Participants: | |||||
| Linked BF Score: | 24 | ||||
| Description |
|
Even though the lookup in _configsvrRemoveShard might have returned a shard object, due to concurrently running removeShard or due to the ShardRegistry not being causally-consistent, it could happen that the particular shard is removed by the time the execution reaches this line later on in the command. |
| Comments |
| Comment by Githook User [ 02/Dec/19 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}Message: |