[DOCS-3890] Behavior of movePrimary unclear Created: 11/Aug/14 Updated: 16/Mar/15 Resolved: 12/Sep/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.11 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andre Spiegel | Assignee: | Andrew Aldridge |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 22 weeks, 5 days ago | ||||
| Description |
|
The documentation of movePrimary contains several cryptic warnings when it should or shouldn't be used, but doesn't actually explain what it does or doesn't do. http://docs.mongodb.org/manual/reference/command/movePrimary/ What it actually does is move all unsharded collections from the old primary shard to the new primary shard, but it does so without any synchronization or other protection, and therefore the command cannot be used on a live system, since the results of reads and writes on the affected database would be undefined while the move is in progress. This needs to be explained clearly in the documentation, while some of the warnings (such as, "only use this when removing a shard") should be dropped. |
| Comments |
| Comment by Githook User [ 12/Sep/14 ] |
|
Author: {u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |