[SERVER-53521] Verify the temporary resharding collection's contents remained the same after the rename Created: 24/Dec/20  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Max Hirschhorn Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: PM-234, PM-234-M3, PM-234-T-fuzzer, cs-subteam1, sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Cluster Scalability
Participants:

 Description   

This would be added to the ReshardingTest fixture. ReshardingTest#_checkConsistency() compares the contents of the existing sharded collection with the temporary resharding collection. It is conceivable (albeit unlikely) that the sharded collection ends up with different contents than what was in the temporary resharding collection. For completeness, we should also confirm that the contents of the existing sharded collection after the reshardCollection command has returned match the contents of the temporary resharding collection previously read. Max's thought would be to either run the dbHash command for the particular namespace before and after or $out the contents of the temporary resharding collection and use DataConsistencyChecker.getDiff().


Generated at Thu Feb 08 05:31:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.