Make _configsvrRefineCollectionShardKey return if shard key is already refined before checking for StaleEpoch

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.1
    • Affects Version/s: 4.3 Required
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2019-08-26
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      A config server stepdown may cause the mongos to retry _configsvrRefineCollectionShardKey even though it has successfully refined the shard key. This results in a StaleEpoch error. Checking that the shard key has already been refined before checking for a StaleEpoch error will fix this bug.

            Assignee:
            James Heppenstall (Inactive)
            Reporter:
            James Heppenstall (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: