Currently, if the migration aborts, the hook just assumes that it was caused by the failpoint abortTenantMigrationBeforeLeavingBlockingState but that might not the case. The hook should check the abort reason here to make sure that the migration doesn't abort due to other issues.
- related to
-
SERVER-55167 Investigate why tenant migrations can get DuplicateKey error when run with background_unique_indexes.js
- Closed
-
SERVER-55168 Allow tenant migration cloner to write to system.views collections
- Closed
-
SERVER-55169 Timeseries bucket collections is expected to fail tenant migration cloner's non-empty id index check
- Closed