On Jan 12, 2016, at 9:11 AM, Markus Stockhausen <stockhausen@collogia.de> wrote:
Von: Vinzenz Feenstra [vfeenstr@redhat.com] Gesendet: Dienstag, 12. Januar 2016 09:00 An: Markus Stockhausen Cc: users@ovirt.org; Mike Hildebrandt Betreff: Re: [ovirt-users] NFS IO timeout configuration
Hi there,
we got a nasty situation yesterday in our OVirt 3.5.6 environment. We ran a LSM that failed during the cleanup operation. To be precise when the process deleted an image on the source NFS storage.
...
Reading the docs I got the idea that vdsm default 60 second timeout for IO operations might be changed within /etc/vdsm/vdsm.conf
[irs] process_pool_timeout = 180
Can anyone confirm that this will solve the problem?
Well it will increase the time to 3 minutes and takes effect after restarting vdsm and supervdsm - If that is enough that might depend on your setup.
Thanks Vinzenz,
maybe my question was not 100% correct. I need to know, if this parameter really influences the described timeout behaviour. The best value of the parameter must be checked of course.
Well I might be wrong, but from what I can see that is the right value to configure this.
Markus<InterScan_Disclaimer.txt>