[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:
Duplicate
is duplicated by SERVER-32514 Cluster mergeChunk command should pas... Closed
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: SERVER-28261 Make MongoS send epoch as part of the `mergeChunks` command
Branch: master
https://github.com/mongodb/mongo/commit/0f4309a6c45e9572733091f84d53f76b52e4c89c

Generated at Thu Feb 08 04:17:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.