Hunt, Gary wrote:
I tried restarting qdiskd and I even tried using luci to remove the node from
the cluster and add it back in.
I just tried qdiskd and then rgmanager and it looks like it works. I
just tested one time on a particular cluster so I am not sure if any
other factor on this clust
Hi!
There was an extensive network failure in our network, which stopped the
traffic for a couple minutes in both halves of our heartbeat (or, actually,
token) network. After the connection was restored, each node refused to let the
other nodes rejoin the cluster because they had 'existing state'
I am using a RHEL 5.2 cluster. Using GFS. I am see'ing all 8 of my
nodes with the following processes taking a lot of cpu time:
aisexec
cman_tool (multiple instances per node)
Do folks see those two processes hogging the cpu normally? All the
time??
Ed
--
Linux-cluster mailing
This is my cluster.conf.
I tried restarting qdiskd and I even tried using luci to remove the node from
the cluster and add it back in.
-Original Message-
From: linux-cluster-boun...@redhat.com
[mailto:linux-cluster-boun...@redhat.com] On Behalf Of Vu Pham
Sent: Wednesday, March 18, 2009 7:14 PM
To: linux cluster
carlopmart wrote:
Hi all,
i have setup a cluster with two nodes and I need to modify when the
service's status is checked. To do this I have put this on cluster.conf:
recovery="relocate">
Mikko Partio wrote:
2009/3/19 mailto:harri.paivani...@tieto.com>>
""Also, if I shut down both nodes and start just one of them, the
starting node still waits in the "starting fencing" part many
minutes even though the cluster should be quorate (there's a quorum
disk)!
""
I made a support query to official RH support for that,
but they just couldn't understand what I was saying and after all they
said "it's normal" ;)
To my mind it was a bug... but this was what RH support answered:
" The problem with starting a cluster with one node and qdisk is that there
nee
