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

listCollections command through mongos should retry on NotMaster errors

    XMLWordPrintableJSON

Details

    • Sharding EMEA

    Description

      Currently, the listCollections command on mongos uses DBClientReplicaSet::query, which does not retry on NotMaster errors.

      This is a problem for concurrency stepdown suites (like the config stepdown suite introduced in SERVER-30677), that call listCollections through mongos as part of validating the state of the cluster between workloads, and because shardCollection, which is also called between workloads, involves calling listCollections and can fail if the config server has a stale view of the cluster.

      The same is true for listIndexes, which uses the same cursorCommandPassthrough helper.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-36325 mongos will not retry configsvrShardCollection when it gets a not master error calling listIndexes

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

          Task - A task that needs to be done. SERVER-33514 send dbVersion on listCollections and listIndexes

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

          Task - A task that needs to be done. SERVER-72868 Complete TODO listed in SERVER-30949

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

          Activity

            People

              backlog-server-sharding-emea Backlog - Sharding EMEA
              jack.mulrow@mongodb.com Jack Mulrow
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: