[SERVER-52931] [Resharding] Verify, in the resharding test fixture, that the collection with a non-original UUID exists on recipient shards after resharding completes Created: 18/Nov/20 Updated: 29/Oct/23 Resolved: 12/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Blake Oler | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-T-lifecycle | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | Sharding 2021-01-25 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Story Points: | 1 | ||||||||||||||||||||||||
| Description |
|
There's a separate data consistency check we already have implement to verify the config.collections info is consistent with listCollections on the shards so the combination of knowing the collection exists with a new UUID in combination with the title is sufficient. |
| Comments |
| Comment by Githook User [ 12/Jan/21 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: |
| Comment by Max Hirschhorn [ 26/Dec/20 ] |
I feel like coverage of the temporary resharding collection being renamed is provided by a combination of https://github.com/mongodb/mongo/blob/dcaaf0305d3b65b023a84e9ac7ac92f8649b07de/jstests/sharding/libs/resharding_test_fixture.js#L224-L227 and the check_uuids_consistent_across_cluster.js hook. I'm not sure there's much additional value in reshard_collection_basic.js being updated. I think reshard_collection_basic.js could instead focus on the different syntax options for the reshardCollection command. |