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

Refresh after chunk migration commit may not see the committed metadata

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical - P2
    • Resolution: Fixed
    • 3.4.16, 3.6.6, 4.0.0, 4.1.1
    • 3.4.17, 3.6.7, 4.0.1, 4.1.2
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.0, v3.6, v3.4
    • Sharding 2018-07-30
    • 0

    Description

      The chunk migration logic uses the CatalogCache to refresh the metadata after issuing the commit against the config server. SERVER-33954 uncovered that the catalog cache's "WithRefresh" methods are not causally consistent and because of this, it is possible that a refresh after chunk migration commit could join a concurrent refresh and not see its own changes.

      This should be backported together with SERVER-36132.

      Attachments

        Issue Links

          Activity

            People

              kaloian.manassiev@mongodb.com Kaloian Manassiev
              kaloian.manassiev@mongodb.com Kaloian Manassiev
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: