Hi all,
*Quorum - *
The questions are bit theoretical, I have gone through documentation and man
pages and have understood that, a cluster is "quorate" if a cluster or its
partition has nodes, with votes equal to or more than "expected_votes" in
"cman" section of cluster.conf file (with no require
Hi Steven,
As near as I can tell, the access times aren't getting updated, but when
I run BLAST on a second node, it also gets an EX lock on the inode. On
the other hand, if I run them simultaneously, they both get shared (SH)
locks (!?!):
node1:
lsof:
blastp21730root memREG 2
Hi
There was recently a thread about evictions due to multipath timeouts
with qdisk, it's in the " Re: [Linux-cluster] RHCS Multipath / Fence"
thread. The pointed RHN docs aids over suggested timings in
multipath.conf to try avoid these issues, perhaps it would help.
regards,
alvaro
-Mens
Hi,
On Mon, 2011-01-17 at 11:06 -0800, Scooter Morris wrote:
> Steven,
> Thanks for getting back to me. Yes, I've checked and noatime is
> definitely set. While blast was running, I did a lockdump and the
> mmaped files had EX locks on them:
>
> G: s:EX n:2/5497229 f:q t:EX d:EX/0 l:0 a
I we have several redhat cluster running cman-2.0.115-34.el5 and yesterday
we faced and incident I cant figure it out:
We have 2node cluster+qdisk connected through iscsi with dual paths
we had some network issue and one of paths to the quorum disk was
unavailable. after that I see some qdisk evic