[SERVER-7394] 'movePrimary' should issue a warning if data exists in the database being moved Created: 17/Oct/12 Updated: 13/Aug/13 Resolved: 11/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Zola | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
This is an extension to The long-term fix would be to lock all of the collections being moved by 'clone'. As a short-term fix, I'd suggest having 'movePrimary' return a warning if it detects any unsharded collections in the database being moved. |
| Comments |
| Comment by Remon van Vliet [ 13/Aug/13 ] |
|
Is there an open issue for the long term fix suggested here? |
| Comment by Scott Hernandez (Inactive) [ 11/Mar/13 ] |
|
"movePrimary" needs to move unsharded collections (with data) in the source database/shard to a new shard. Your request directly contradicts the purpose of the "movePrimary" command. |