[SERVER-26176] shardCollection can create shard index in the wrong shard Created: 19/Sep/16 Updated: 01/Mar/18 Resolved: 01/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.3.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
After a movePrimary, if a mongos that is not aware of it receives a shardCollection command on an empty collection, it can create the shard key index on the old primary shard of the database. |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 01/Mar/18 ] |
|
Closing as "gone away" because shardCollection now takes the database distlock, as does movePrimary. |