[SERVER-9776] Block migrations on hashed shardkeys where MongoD is not 2.4 Created: 24/May/13 Updated: 10/Dec/14 Resolved: 28/Jun/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Hows | Assignee: | Daniel Pasette (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
One 2.2 Shard Server (shard0001) db.test2.drop() )} ); ); ); , "shard0001"); ); , "shard0000"); ) |
||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
If you run a sharded cluster with one shard running 2.2 and one shard running 2.4 you can end up with invalid chunk migrations. This happens as the 2.2 node incorrectly processes the moveChunk command on the hashed shard key and does not correctly find all documents which should be migrated. This can potentially leave whole chunks orphaned. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 28/Jun/13 ] |
|
There doesn't appear to be a clean way to prevent this at this point. |