Hello Vinzenz Feenstra, Francesco Romani,
I'd like you to do a code review. Please visit
https://gerrit.ovirt.org/55786
to review the following change.
Change subject: migrations: change migration parameters
......................................................................
migrations: change migration parameters
Changed the migration params to:
max_outgoing/incoming_migrations=2
migration_max_bandwidth=52
migration_progress_timeout=240
migration_downtime_delay=20
migration_downtime_steps=5
The reason to change migration_max_bandwidth and
max_outgoing/incoming_migrations is to have less migrations running in parallel
faster which helps convergence.
The reason to change the migration_progress_timeout is to leave more time for
big VMs to converge.
The reason to change migration_downtime_delay is to make the downtime thread
start applying the changes faster which is important for VMs which would start
stalling.
The reason to change the migration_downtime_steps is to make the growing of the
downtime more fast.
Change-Id: I1ed1b04ee77a7144ae0206e5c5ae1426ede0c75f
Bug-Url: https://bugzilla.redhat.com/1323952
Signed-off-by: Tomas Jelinek <tjeli...@redhat.com>
Reviewed-on: https://gerrit.ovirt.org/55676
Reviewed-by: Vinzenz Feenstra <vfeen...@redhat.com>
Continuous-Integration: Jenkins CI
Reviewed-by: Francesco Romani <from...@redhat.com>
---
M lib/vdsm/config.py.in
1 file changed, 5 insertions(+), 5 deletions(-)
git pull ssh://gerrit.ovirt.org:29418/vdsm refs/changes/86/55786/1
diff --git a/lib/vdsm/config.py.in b/lib/vdsm/config.py.in
index 3156343..c3c893a 100644
--- a/lib/vdsm/config.py.in
+++ b/lib/vdsm/config.py.in
@@ -70,7 +70,7 @@
('migration_destination_timeout', '21600',
'Maximum time the destination waits for the migration to finish.'),
- ('migration_progress_timeout', '150',
+ ('migration_progress_timeout', '240',
'Maximum time the source host waits during a migration in case '
'that there is no progress. If the time has passed, the migration '
'will be aborted.'),
@@ -84,7 +84,7 @@
'Time to wait (in seconds) for migration destination to start '
'listening before migration begins.'),
- ('migration_max_bandwidth', '32',
+ ('migration_max_bandwidth', '52',
'Maximum bandwidth for migration, in MiBps, 0 means libvirt\'s '
'default, since 0.10.x default in libvirt is unlimited'),
@@ -115,16 +115,16 @@
'liveness of migration, set to a very high value, such as '
'600000.'),
- ('migration_downtime_delay', '75',
+ ('migration_downtime_delay', '20',
'This value is used on the source host to define the delay before '
'setting/increasing the downtime of a migration. '
'The value is per GiB of RAM. A minimum of twice this value is '
'used for VMs with less than 2 GiB of RAM'),
- ('migration_downtime_steps', '10',
+ ('migration_downtime_steps', '5',
'Incremental steps used to reach migration_downtime.'),
- ('max_outgoing_migrations', '3',
+ ('max_outgoing_migrations', '2',
'Maximum concurrent outgoing migrations'),
('sys_shutdown_timeout', '120',
--
To view, visit https://gerrit.ovirt.org/55786
To unsubscribe, visit https://gerrit.ovirt.org/settings
Gerrit-MessageType: newchange
Gerrit-Change-Id: I1ed1b04ee77a7144ae0206e5c5ae1426ede0c75f
Gerrit-PatchSet: 1
Gerrit-Project: vdsm
Gerrit-Branch: ovirt-3.6
Gerrit-Owner: Tomas Jelinek <tjeli...@redhat.com>
Gerrit-Reviewer: Francesco Romani <from...@redhat.com>
Gerrit-Reviewer: Vinzenz Feenstra <vfeen...@redhat.com>
_______________________________________________
vdsm-patches mailing list
vdsm-patches@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-patches
