-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
We should strive to add more test coverage for restoring backups with concurrent sharding DDL operations. This ticket is to add targeted jstest(s) for running magic restore on a backup that was taken during a sharded createCollection and createDatabase operations. If we can combine these into one test, we should. Otherwise, two separate tests is OK.magic_restore_non_pit_moveprimary.js is an example of a sharding DDL test with restore for the movePrimary operation. non-PIT and PIT are not as relevant for these tests, so targeting non-PIT for simplicity is sufficient.
When testing this, we should run magic restore with shard renames, and double check all relevant sharding metadata to ensure the name change was successful.