Set a running migration limit
Setting a running migration limit is designed to control how many data migrations can run simultaneously, excluding those in a live or recurring state, with the aim of reducing the load on the namenode that may result from many concurrently scanning migrations.
Data Migrator starts more migrations as previously-started migrations reach a LIVE state. High priority migrations are processed first, followed by Normal and Low priority migrations. Migrations with the same priority start in order of creation date, oldest to newest. See Prioritize migrations for more information on migration priorities.
Creating new migrations can affect the order of migrations waiting to start and can impact currently running migrations. For example, with a migration limit of 1, and 1 lower-priority migration running, when a new higher-priority migration is started, Data Migrator will move this new migration to the RUNNING state. The lower-priority migration will remain running but Data Migrator will prioritize processing of the higher-priority migration.
You must have the admin role assigned to update the running migration limit.
Set a running migration limit with the UI
- On the Dashboard page, select the relevant instance from the Instances panel.
- Select Data Migrations from the Migrations menu on the left side.
- Under Running Migrations, enter the number of migrations you want to be able to run simultaneously. This number excludes migrations in a live or recurring state.info
The default migration limit is 10. Setting the Running Migration Limit value to
0indicates no limit. - Select Save.
Set a running migration limit with the CLI
Set a running migration limit with the CLI by running the following command:
configuration set --key migration.max.running.migrations --value 15
Check the current running migration limit by running the following command:
configuration get --key migration.max.running.migrations