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

Don't replace the ShardRegistry with older information than it already knows about

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.2.0-rc0
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding B (10/30/15)
    • 0

    Description

      If two calls to ShardRegistry::reload() overlap, it's possible for one that started sooner and targeted a staler node to finish after one that started later. This means that the ShardRegistry could already have been loaded with newer data, but then throw it out and replace it with older data when the slower reload finishes.

      Attachments

        Activity

          People

            spencer@mongodb.com Spencer Brody (Inactive)
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: