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

mongos_get_shard_version.js assumes causal consistency but isn't

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • v4.4
    • Sharding 2020-04-20
    • 22

    Description

      Test performs splits, moveChunk and checks the version of the mongos at the end to make sure that mongos has the version right before the moveChunk. The issue is that the splitChunk command are sent directly to the shards, this means that when mongos performs a force refresh at the beginning of moveChunk, it can get a version that is even older. And this will cause the assertion at the end to fail.

      Attachments

        Activity

          People

            randolph@mongodb.com Randolph Tan
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: