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

Use invalidateShardForShardedCollection in the router's moveChunk command

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.4
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2020-02-24

    Description

      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.

      Attachments

        Activity

          People

            blake.oler@mongodb.com Blake Oler
            blake.oler@mongodb.com Blake Oler
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: