[SERVER-20742] Stop sending epoch to mongod on move chunk operations Created: 02/Oct/15 Updated: 23/Aug/23 Resolved: 23/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Done | Votes: | 0 |
| Labels: | 7.0UpDown | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 22/Aug/23 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: |
| Comment by Dianna Hohensee (Inactive) [ 20/Jul/16 ] |
|
It looks like moveChunk can't remove the epoch field until 3.6, whereas split can in 3.4. Modified this ticket to handle the moveChunk part, and created |