[SERVER-23764] Reject most operations when a mongod is started with --shardsvr but hasn't yet been added as a shard Created: 15/Apr/16 Updated: 06/Dec/22 Resolved: 09/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
If a mongod is started with --shardsvr but doesn't have a shardIdentity document we should fail all operations except:
|
| Comments |
| Comment by Spencer Brody (Inactive) [ 10/May/16 ] |
|
Actually, this runs the risk of breaking the zero-downtime process for converting an existing replica set to a sharded cluster. |
| Comment by Spencer Brody (Inactive) [ 15/Apr/16 ] |
|
We probably can't do this for 3.4 to preserve compatibility with 3.2, but we should be able to do this in 3.6 |