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

Remove CheckClusterIndexConsistency hook from concurrency_sharded_initial_sync.yml test suite

XMLWordPrintableJSON

    • Cluster Scalability
    • Fully Compatible
    • Cluster Scalability 06/24/24, Cluster Scalability 2024-07-08, Cluster Scalability 2024-07-22, Cluster Scalability 2024-08-19, Cluster Scalability 2024-09-02
    • 0
    • 1

      The lack of synchronization between createIndexes and dropIndexes is known to result in cases where shards may permanently have differing indexes. FSM workloads, such as snapshot_read_catalog_operations.js, which run as part of the concurrency framework are capable of executing concurrent createIndexes and dropIndexes commands on the same collection and can trigger this type of inconsistency. We should remove the validation from the CheckClusterIndexConsistency hook until the guarantees provided by sharded clusters are strengthened.

            Assignee:
            israel.hsu@mongodb.com Israel Hsu
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: