[SERVER-12515] Unable to move hashed shard key chunks created by numInitialChunks Created: 28/Jan/14 Updated: 11/Jul/16 Resolved: 18/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.9, 2.5.1, 2.5.5 |
| Fix Version/s: | 2.4.10, 2.6.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | hashed, numInitialChunks | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
| Comments |
| Comment by Björn Bullerdieck [X] [ 08/Apr/14 ] |
|
I think there is still a thread a problem-when simultaneously create several sharded collections ( |
| Comment by Randolph Tan [ 07/Apr/14 ] |
|
Hi dmurphy, We just corrected the error in the description. If you are using hashed shard keys, I highly recommend upgrading to 2.4.10. Thanks! |
| Comment by David Murphy [ 07/Apr/14 ] |
|
This is wrong ALL move Chunks are affected in 2.4.6. Resulting in a broken balancer until the max chunk shard is stepped down. This is because the max chunk thinks it owns all chunks Sent from my iPhone |
| Comment by Daniel Pasette (Inactive) [ 12/Mar/14 ] |
|
dmurphy: here is the exact commit: It can be found on the v2.4 branch. 2.4.10 is still not a release candidate. |
| Comment by David Murphy [ 12/Mar/14 ] |
|
Thanks Randolph, Erik and I were planning to look at that today. Is the branch currently the 2.4.10 or 2.4.9 base in the repo (2.4.10¹s |
| Comment by Randolph Tan [ 12/Mar/14 ] |
|
dmurphy I just backported the fix to the v2.4 branch so you can just clone the repo and build the source on that branch. |
| Comment by Githook User [ 11/Mar/14 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Backport fix for commit 3a08be3bf2a1a650c97543a448a8ea0c143a89b6 |
| Comment by Daniel Pasette (Inactive) [ 05/Mar/14 ] |
|
It hasn't been backported yet. When it is (and this is being worked on this week), it will be listed as a public comment on this ticket. Without having done the backport yet, I can't say exactly what the code will look like. |
| Comment by David Murphy [ 04/Mar/14 ] |
|
I know this will be back ported, as you have it listed as 2.4.10 in fixed If we don¹t have this I will need to just make a patch based on the 2.6 David |
| Comment by Randolph Tan [ 04/Mar/14 ] |
|
It will be backported to 2.4.10. |
| Comment by David Murphy [ 03/Mar/14 ] |
|
I see this was tagged with 2.4.10, was this still using commit 3a08be3bf2a1a650c97543a448a8ea0c143a89b6, or is there a new commit for the 2.4.10 version of this? |
| Comment by Githook User [ 18/Feb/14 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |