[SERVER-7358] Pre-split new collections when using a hashed shard key Created: 15/Oct/12 Updated: 05/Jun/13 Resolved: 20/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.3.0 |
| Fix Version/s: | 2.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Matulef | Assignee: | Kevin Matulef |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
When using a hashed shard key on a new collection, we can pre-split the range into many chunks, and redistribute those chunks before data is inserted, to avoid shuffling data around later. Users can currently do this manually by calling the 'split' command before inserting data, but we should do it automatically on new collections. |
| Comments |
| Comment by auto [ 20/Nov/12 ] |
|
Author: {u'date': u'2012-11-20T21:47:43Z', u'email': u'matulef@gmail.com', u'name': u'Kevin Matulef'}Message: |
| Comment by auto [ 20/Nov/12 ] |
|
Author: {u'date': u'2012-11-20T20:49:38Z', u'email': u'matulef@10gen.com', u'name': u'Kevin Matulef'}Message: An earlier commit ensured that shardcollection only put initial |
| Comment by auto [ 20/Nov/12 ] |
|
Author: {u'date': u'2012-11-20T19:46:03Z', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}Message: |
| Comment by auto [ 20/Nov/12 ] |
|
Author: {u'date': u'2012-11-20T03:41:48Z', u'email': u'matulef@gmail.com', u'name': u'Kevin Matulef'}Message: |
| Comment by auto [ 20/Nov/12 ] |
|
Author: {u'date': u'2012-11-20T00:37:26Z', u'email': u'matulef@gmail.com', u'name': u'Kevin Matulef'}Message: |
| Comment by auto [ 16/Nov/12 ] |
|
Author: {u'date': u'2012-11-16T00:31:27Z', u'name': u'Kevin Matulef', u'email': u'matulef@gmail.com'}Message: |