checkUUIDsConsistentAcrossCluster must retry on NotMaster errors

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • 4.3 Desired
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding EMEA
    • Sharding 2017-12-04, Sharding 2017-12-18
    • 15
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The UUID check is failing because slow machines can cause unexpected shard primary step downs, and the UUID check does listCollections directly against the shard, which only runs on a primary and returns NotMaster if the expected primary is no longer primary.

      SERVER-31583 and SERVER-31385 are related checkUUIDsConsistentAcrossCluster problems.

            Assignee:
            [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: