[SERVER-81596] Fix Race in index_operations_abort_concurrent_outgoing_migrations.js Created: 29/Sep/23 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Brett Nawrocki | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | cs-subteam1, sharding-nyc-subteam1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Cluster Scalability
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 6 | ||||
| Story Points: | 2 | ||||
| Description |
|
When featureFlagShardKeyIndexOptionalHashedSharding is enabled, index_operations_abort_concurrent_outgoing_migrations.js will drop the shard key index and verify it both aborts the chunk migration and that the index is dropped on both shards. However, it is possible that the recipient will recreate the index before it is dropped on the donor, thus allowing it to persist even after chunk migration is aborted. This will cause the associated assertion to fail in the test. |