[SERVER-30402] createCollection on mongos can create an unreachable collection if movePrimary has been called Created: 28/Jul/17 Updated: 06/Dec/22 Resolved: 01/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
createCollection on mongos does not check for the collection's existence in the cluster; it simply forwards the create command to (what it believes is) the database's primary shard. If movePrimary has been called from another mongos, this mongos will cause the collection to be created on the wrong (old primary) shard, leaving it unreachable. I believe once |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 01/Mar/18 ] |
|
Closing as a dupe of CC janna.golden |