[SERVER-3562] moveprimary moves all databases, including sharded collections Created: 09/Aug/11 Updated: 12/Jul/16 Resolved: 29/Mar/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 1.8.2, 1.9.2 |
| Fix Version/s: | 2.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
Issuing a movePrimary command should only move unsharded collections, sharded collections are required to be drained first. Potentially also affects new versions. Can reproduce easily in a sharded setup, shard a collection, then issue movePrimary to another shard. The first shard will be empty, the second shard will have the data, and the chunks collection will not be updated. |
| Comments |
| Comment by auto [ 29/Mar/12 ] |
|
Author: {u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by Greg Studer [ 06/Mar/12 ] |
|
CodeReview @ http://codereview.10gen.com/7506039/ |
| Comment by Greg Studer [ 05/Feb/12 ] |
|
small fix for basic safety, fuller fix is very complex. |