[SERVER-21851] 3.0 mongos allows movePrimary for admin database Created: 10/Dec/15 Updated: 14/Dec/15 Resolved: 14/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
mongos 3.0.x allows to
This issue is implicitly fixed in mongos 3.2. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 10/Dec/15 ] |
|
What happens after running movePrimary on the admin db? Is the existing data in the admin db actually moved to the shard? Do future read/writes get routed correctly to the config servers, or do they start being routed to the shard? |