Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-20742

Stop sending epoch to mongod on move chunk operations

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding EMEA
    • Fully Compatible
    • 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
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None