Am 08.09.2015 um 11:20 hat Fam Zheng geschrieben:
[Cc'ing address@hidden
On Tue, 09/08 11:00, Denis V. Lunev wrote:
To avoid such situation this patchset introduces patch per-drive option
"disk-deadlines=on|off" which is unset by default.
The general idea sounds very nice. Thanks!
Should we allow user configuration on the timeout? If so, the option should be
something like "timeout-seconds=0,1,2...". Also I think we could use werror
and rerror to control the handling policy (whether to ignore/report/stop on
timeout).
Yes, I think the timeout needs to be configurable. However, the only
action that makes sense is stop. Everything else would be unsafe because
the running request could still complete at a later point.
Another question I have related to safety is whether (and how) you can
migrate away from a host that has been stopped because of a timeout. I
guess migration needs to be blocked then?
Kevin