[SERVER-84303] Give a better indication of why a moveChunk operation has failed Created: 19/Dec/23  Updated: 08/Jan/24

Status: Needs Scheduling
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Lamont Nelson Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: cs-subteam2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-84434 Chunk migration may fail due to index... Open
Assigned Teams:
Cluster Scalability
Participants:
Story Points: 3

 Description   

When moving a chunk we rely on IndexCatalog::removeExistingIndexesNoChecks to determine if the indexes are the same between the source and destination. Upon inspecting why the exception occurred in a customer case it seemed like both sides had the same indexes when using commands such as getIndexes. This ticket is to improve this situation such that we are given better diagnostic information in the error or getindexes output.


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