Use invalidateShardForShardedCollection in the router's moveChunk command

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2020-02-24
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We try to move the routingInfo twice in the router's moveChunk command. This is invariably a bug. We don't need to go through the onStaleShardVersion() path in order to invalidate this collection – we can use invalidateShardForShardedCollection() in order to achieve the same result, which is marking the shard as stale.

            Assignee:
            Blake Oler
            Reporter:
            Blake Oler
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: