[SERVER-25762] Failing to add databases discovered from a newly added shard to the cluster doesn't cause the addShard to fail Created: 23/Aug/16 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ShardingRoughEdges, high-value, oldshardingemea | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Catalog and Routing
|
||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2020-10-19, Sharding 2020-11-02, Sharding 2020-11-16, Sharding 2020-11-30, Sharding 2020-12-14, Sharding 2020-12-28, Sharding 2021-01-11 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
During addShard we find any databases that already exist on the shard being added and attempt to add them to the cluster. If this fails for any reason, however, we log a message and continue. This feels like a bad idea as now a) databases that a user might have been expecting to be visible to the cluster are now hidden and b) while I have not verified this, I suspect this could cause problems if a database with the same name is created sometime in the future. |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 19/Dec/19 ] |
|
This is where the config server attempts to add the new shard's databases to config.databases. |