Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
ALL
-
Sharding EMEA 2022-02-07
Description
The test is wrongly using the "hangInRefreshFilteringMetadataUntilSuccessInterruptible" to hang the migration, in fact this fail point is used twice in the migration code and it will cause the migration to block earlier then the test is expecting. So the test hang for 10 min and it work by accident just because the periodicConsistencyChecker is triggering a migration recovery after 10 min.