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

Stop forcing routing info refresh in cluster moveChunk command

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding EMEA
    • ALL

    Description

      Stop forcing a routing info refresh at the very beginning of cluster moveChunk command we should rely on the shard versioning protocol that will ensure that eventually the mongos will retry the command according to the updated routing info

      Attachments

        Activity

          People

            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: