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

XMLWordPrintableJSON

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

      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.

              Assignee:
              Jack Mulrow
              Reporter:
              Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: