Hi
Yes Lars, but in fact it seems that the problem is not in the monitoring
of SAN resources managed under Pacemaker, but on corosync management of
heartbeat tokens during such IO loads on SAN
Regards
Alain
Le 02/10/2013 15:08, Lars Marowsky-Bree a écrit :
On 2013-10-02T13:40:16, Ulrich Windl <[email protected]> wrote:
There is one notable exception: If you have shared storage (SAN, NAS, NFS), the
cause of the slowness may be external to the systems being monitored, thus
fencing those will not improve the situation, most likely.
True. Alas, the cluster stack doesn't magically know that, but must be
told - to either allow for long enough timeouts for services on such
media (because even then, the slowness maybe external, or caused
internally), or to not monitor them.
Regards,
Lars
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
