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

MongoS initiated metadata refreshes not based on StaleConfig error may see stale config data

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.9
    • Affects Version/s: 3.2.14, 3.4.5, 3.5.8
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • 0

      MongoS write commands may trigger metadata refresh based on errors other than StaleConfig. In particular, this is what's happening in the coll_epoch_test1.js test.

      If a collection gets unsharded on one mongos and a write is scheduled against a different mongos, the second mongos will use a stale config server optime. Because of this, if that read hits a stale config server secondary, it won't see the change in the sharding state.

      This is an inherent problem, which can only be solved through the support in the causal consistency project, so this ticket is filed just as a placeholder for versions prior to 3.6.

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

              Created:
              Updated:
              Resolved: