[SERVER-13385] relax merge chunk constraints Created: 27/Mar/14 Updated: 27/Sep/16 Resolved: 15/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | cap-ticket-needed | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
To be paranoid, we limited chunk merging to empty chunks, and only two-at-a-time. We should probably revisit this once merging chunks have had some burn-in time to provide inverse functionality to split chunk (merge multiple). In particular it's awkward and racy to try and validate that one of the merged chunks has no data. |
| Comments |
| Comment by Randolph Tan [ 10/Sep/14 ] |
|
To docs: In addition, merging of more than 2 chunks is also now allowed. |
| Comment by Randolph Tan [ 15/May/14 ] |
|
To docs: merging non empty chunks are now allowed. |
| Comment by Githook User [ 15/May/14 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |