[SERVER-19037] create command fails on mongos immediately following a dropDatabase command on another Created: 18/Jun/15 Updated: 14/Apr/16 Resolved: 31/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.1.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Kaloian Manassiev |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
After dropping a database on one mongos, collection creation fails on a different mongos with the error:
This does not occur on 3.0. |
| Comments |
| Comment by Kaloian Manassiev [ 31/Jul/15 ] | |||||||||
|
The scenario described works. I verified it with the following script, with both sharded and unsharded collections:
|