[SERVER-10866] Figure out split triggering mechanism Created: 24/Sep/13 Updated: 06/Dec/22 Resolved: 28/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Plan for 2.6: Plan for beyond 2.6: Eventually, a separate entity will be tasked to keep track of the document sizes being inserted. This entity will have no knowledge of the entire chunk ranges and config for a collection and will only know ranges being fed to it. Basically, the api would look something like:
|
| Comments |
| Comment by Randolph Tan [ 28/Jul/17 ] |
|
Actual work is now tracked in PM-33 |
| Comment by auto [ 12/Nov/13 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Enable update auto aplit test. |
| Comment by auto [ 30/Oct/13 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Wire auto-split logic for update write commands. |
| Comment by auto [ 25/Oct/13 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Implement auto-split for insert write commands on mongos. Note that this patch currently also take documents from the delete commands into account as well (this will be fixed in the next iteration). However, deletes will never trigger an auto-split request. |