-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This code, found here,
unpauseMigrateAtStep(shard1, migrateStepNames.cloned);
assert.eq(2, shard0Coll3.count(), "donor shard0 completed a migration that it aborted");
assert.eq(1,
shard1Coll3.count(),
"shard1 accessed the xfermods log despite " + "donor migration abortion");
should do a pause at catchup step, then unpause clone, and wait for catchup before doing the count asserts.
This won't fail the migration_ignore_interrupt.js test, and it's merely a testing issue: not testing it right.