3.4 also needs to send an "epoch" field separately from within the "shardVersion" field to maintain backwards compatibility with 3.2, which expects and requires an "epoch" field in a moveChunk command. After 3.4 is released, we can safely remove the "epoch" field from moveChunk commands.
- is related to
-
SERVER-25174 Stop sending epoch to mongod on spilt chunk operations
-
- Closed
-
- related to
-
SERVER-25170 Make moveChunk commands append an "epoch" field
-
- Closed
-
-
SERVER-65645 IDL-ify all commands on the chunk migration path
-
- Closed
-