[SERVER-28261] The `mergeChunks` command should send epoch end-to-end Created: 09/Mar/17 Updated: 25/Apr/18 Resolved: 19/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2018-04-23 | ||||||||
| Participants: | |||||||||
| Description |
|
Mongod mergeChunks command already uses an optional 'epoch' command field. This is basically a line or two addition to the cluster command to include the field. For v3.8 we can make the mongod mergeChunks command require the 'epoch' field, making it no longer optional. We cannot do this is v3.6 because we must maintain backwards compatibility with a v3.4 mongos not sending the 'epoch' field. |
| Comments |
| Comment by Githook User [ 19/Apr/18 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm', 'name': 'Kaloian Manassiev'}Message: |