Ensure a migration can be interrupted within reasonable time at any stage
Users who have pulp 2 and pulp 3 on the same machine need to have a way to control when migration is running. The migration plugin inevitably provides certain load on the system and uses resources. Users might want to choose windows when they run a migration. E.g. Run every Saturday for 4 hours at most.
If the system is large, it can take hours to migrate it, users need a way to cancel the task and free all the related resource within a reasonable timeframe.
When there is a very slow db query and the task which triggered that query is cancelled, how quickly the db query will be aborted as well?
Please register to edit this issue