Stop forcing routing info refresh in cluster moveChunk command

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding EMEA
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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

            Assignee:
            [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: