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

checkUUIDsConsistentAcrossCluster must retry on NotMaster errors

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Won't Do
    • None
    • 4.3 Desired
    • Sharding
    • None
    • Sharding EMEA
    • Sharding 2017-12-04, Sharding 2017-12-18
    • 15

    Description

      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.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31643 Make drop collection in concurrency workloads retry LockBusy errors

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31385 ShardingTest.prototype.checkUUIDsConsistentAcrossCluster not resilient to closed connections

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-31583 Update ShardingTest._connections when a replica set is restarted

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-sharding-emea Backlog - Sharding EMEA
              dianna.hohensee@mongodb.com Dianna Hohensee
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: