[SERVER-72271] Remove CheckClusterIndexConsistency hook from concurrency_sharded_initial_sync.yml test suite Created: 20/Dec/22 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 6 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
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. |