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

Index consistency check at end of sharding tests isn't robust to ShardNotFound

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • v4.4
    • Sharding 2020-09-21
    • 0

    Description

      The balancing_sessions_collection.js intentionally removes one of the shards before shutting down the ShardingTest. It is possible for mongos to refresh its ShardRegistry after choosing to target all shards with the $indexStats aggregation and then triggers a ShardNotFound error.

      One proposal to address this issue is to retry running the $indexStats aggregation on ShardNotFound errors.

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: