Re: qdisk timeouts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello

from the logs seems qdisk could not write to the quorum and got evicted,
normal behavior.
now depends on what you want it to, and fine tune some timmings

cheers
jose


> 2 node cluster with quorum disk running rhcs on rh5.7.
>
> Attempting to debug why we get the following qdisk issues:
> Nov  7 16:24:09 host532 qdiskd[5750]:  qdiskd: write (system call) has
> hung for 13 seconds
> Nov  7 16:24:09 host532 qdiskd[5750]:  In 14 more seconds, we will be
> evicted
> Nov  7 16:24:11 host532 openais[5711]: [CMAN ] lost contact with quorum
> device
> Nov  7 16:24:29 host532 openais[5711]: [CMAN ] cman killed by node 1
> because we were killed by cman_tool or other application
>
> And the node where the time out happens is usually fenced. Is this
> something to do with my qdisk interval/ko timings of:
> quorumd interval="3" label="qdisk" min_score="1" tko="9" votes="1
>
> cluster.conf attached.
>
> Thanks
> Michael
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> Linux-cluster mailing list
> Linux-cluster@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/linux-cluster


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster


[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux