Skip to content
This repository has been archived by the owner on Mar 19, 2021. It is now read-only.

Commit

Permalink
migration: Clarify item about automatic start of migration jobs.
Browse files Browse the repository at this point in the history
The old text was needlessly convoluted.
  • Loading branch information
Andre Noll authored and joergsteffens committed Dec 9, 2015
1 parent 8d23489 commit a54df29
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions manuals/en/main/migration.tex
Expand Up @@ -117,10 +117,10 @@ \section{Important Migration Considerations}
Volumes needed to do Migrations. For the moment, you must take
care as all the resource deadlock algorithms are not yet implemented.

\item Migration is done only when you run a Migration job. If you set a
Migration High Bytes and that number of bytes is exceeded in the Pool
no migration job will automatically start. You must schedule the
migration jobs, and they must run for any migration to take place.
\item Setting the Migration High Bytes watermark is not sufficient
for migration to take place. In addition, you must define
and schedule a migration job which looks for jobs that can
be migrated.

\item If you migrate a number of Volumes, a very large number of Migration
jobs may start.
Expand Down

0 comments on commit a54df29

Please sign in to comment.