On 21 April 2016 at 12:43, Michal Skrivanek <michal.skrivanek@redhat.com> wrote:
max_outgoing_migrations = 3
you should lower this, otherwise it won’t fit (1 migration at 100MBps would eat your whole link already). So use 1
migration_downtime = 1000
it’s not really 1000. There’s a UI for that in Edit VM, so you shouldn’t set it here at all and if you do, the algorithm behind it is not-so-great in <=3.6.5. Use migration_downtime_steps=3 or 5 or something lower to mitigate that wrong algorithm behavior
if you need to overcome a longer peak period of activity, also change migration_progress_timeout to something more than 150s
Thanks so much for the tips Michal, I really appreciate it. I'll have to try these tweaks in my next maintenance window, so I'll post my findings in a few days. Cheers, Ollie