Re: [ovirt-users] Concerns with increasing vdsTimeout value on engine?
----- Original Message -----
From: "Ryan Groten" <Ryan.Groten(a)stantec.com>
To: users(a)ovirt.org
Sent: Friday, July 10, 2015 10:45:11 PM
Subject: [ovirt-users] Concerns with increasing vdsTimeout value on engine?
When I try to attach new direct lun disks, the scan takes a very long time to
complete because of the number of pvs presented to my hosts (there is
already a bug on this, related to the pvcreate command taking a very long
time - https://bugzilla.redhat.com/show_bug.cgi?id=1217401 )
I discovered a workaround by setting the vdsTimeout value higher (it is 180
seconds by default). I changed it to 300 seconds and now the direct lun scan
returns properly, but I’m hoping someone can warn me if this workaround is
safe or if it’ll cause other potential issues? I made this change yesterday
and so far so good.
Hi, no serious issue can be caused by that.
Keep in mind though that any other operation will have that amount of time to complete
before failing on timeout - which will
cause delays before failing (as the timeout was increased for all executions) when not
everything is operational and up as expected (as in most of the time).
I'd guess that a RFE could be opened to allow increasing the timeout of specific
operations if a user want to do that.
thanks,
Liron.
Thanks,
Ryan
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users