Create feature to stop or control the impact of the background migrations on the database
We have faced some background migrations that generated load on the database cluster. We would like to investigate the possibilities to manage better this situation in the future.
The idea of this issue is to find out or improve/generate documentation about the background migrations and how to manage them.
Would be a goal to have the following features :
- Be possible to stop the migration.
- Setup the intervals when the migrations are executed.
- Change the chunks of data that will be affected.
- Pause the migration.