[SERVER-84434] Chunk migration may fail due to indexes having not relevant and invalid index options Created: 27/Dec/23  Updated: 02/Feb/24

Status: Open
Project: Core Server
Component/s: Catalog, Sharding
Affects Version/s: 6.0.0, 5.0.10, 7.0.0, 7.1.0, 7.2.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Benety Goh
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-78369 ignoreUnknownIndexOptions doesn't acc... Closed
is caused by SERVER-65797 Remove invalid index specs in memory ... Closed
Related
related to SERVER-84303 Give a better indication of why a mov... Needs Scheduling
Assigned Teams:
Storage Execution
Operating System: ALL
Sprint: Execution Team 2024-01-22, Execution Team 2024-02-05, Execution Team 2024-02-19
Participants:

 Description   

IndexCatalogImpl::removeExistingIndexesNoChecks() does not account for index_key_validate::repairIndexSpec() to remove invalid index options when it calls _doesSpecConflictWithExisting().

{"s":"W",  "c":"SHARDING", "id":23777,   "ctx":"MoveChunk","msg":"Error while doing moveChunk","attr":{"error":"OperationFailed: Data transfer error: migrate failed: CannotCreateCollection: aborting, shard is missing 1 indexes and collection is not empty. Non-trivial index creation should be scheduled manually"}}


Generated at Thu Feb 08 06:55:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.