[SERVER-68056] Add test to validate shard split resets the replicaSetId Created: 14/Jul/22 Updated: 29/Oct/23 Resolved: 03/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Didier Nadeau | Assignee: | Didier Nadeau |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2022-11-14 |
| Participants: |
| Description |
|
We resets the replica set id to ensure the recipient and donor config do not have the same replicaSetId. We have a test to ensure the utility function resets the ID, but we don't validate shard split itself does. If shard split stops using the utility function, we could conceivably stop resetting the ID without noticing it. We should add a check (in an existing unit test) to verify the replicaSetId is reset. We should also remove shard_split_apply_splitconfig.js as it was meant to test application of the split config (and recipient nodes leaving the set when that happens) before the full shard split worked. This is now down as part of split so the test is not really relevant anymore. |
| Comments |
| Comment by Githook User [ 03/Nov/22 ] |
|
Author: {'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}Message: |