If a migration is aborted between _recvChunkStart and _migrateClone , the recipient might end up cloning indexes and options before it finds out that the migration has been aborted. So for the createIndexes tests, we should not assert that the recipient shard doesn't have the index created on the donor shard during migration.
index_operations_abort_concurrent_outgoing_migrations.js shouldn't assert that the recipient doesn't have the index created on the donor
- Assignee:
-
Cheahuychou Mao
- Reporter:
-
Cheahuychou Mao
- Votes:
-
0 Vote for this issue - Watchers:
-
1 Start watching this issue
- Created:
- Updated:
- Resolved: