Hi all,
another question rised up while reading documentation concerning
2-node-cluster under RHEL6.x with CMAN and pacemaker.
a) In the quick start guide one of the things you set is
CMAN_QUORUM_TIMEOUT=0 in /etc/sysconfig/cman to get one
node of the cluster up without waiting for quorum.
OK, and where is the difference between 1.1.8 and 1.1.7.
I am currently testing this on a one node cluster, so attrd wait for the message come back from himself.
This cant take one second, or is attrd waiting this time anyhow to be sure to get it from all nodes back?
Rainer
Hi
I am doing a rolling upgrade of pacemaker from CentOS 6.3 to 6.4 and
when 1st node is upgraded and gets 1.1.8 version it doesn't join the
cluster and I ended up with 2 clusters.
In the logs of node1 I see
cluster-infrastructure value=classic openais (with pluin)
but node2(still in centos6.3
On 13-04-11 06:00 PM, Andrew Beekhof wrote:
Actually, I think the semantics of -C are first-write-wins and any subsequent
attempts fail with -EEXSIST
Indeed, you are correct. I think my point though was that it didn't
matter in my case which writer wins since they should all be trying to
On 13-04-10 07:02 PM, Andrew Beekhof wrote:
On 11/04/2013, at 6:33 AM, Brian J. Murrell
brian-squohqy54cvwr29bmmi...@public.gmane.org wrote:
Does crm_resource suffer from this problem
no
Excellent.
I was unable to find any comprehensive documentation on just how to
implement a
Hi,
I just finish to install a cluster based on pacemaker for High
available ISCSI target (active/passive), everythinf work like a charm
swictching between nodes, fencing rebooting and disconnecting node.
the cluster runs the following properties ipaddr2, iscsi target, iscsi
lun and drbd.
But
Hello Joseph!
-Ursprüngliche Nachricht-
Von: Joseph-Andre Guaragna [mailto:joseph-an...@rdmo.com]
Gesendet: Freitag, 12. April 2013 17:19
An: pacemaker@oss.clusterlabs.org
Betreff: [Pacemaker] iscsi target mounting readonly on client
You have to make two things absolutely shure.
1.
Hoi,
As I wrote to another post[1] I failed to upgrade to 1.1.8 for a 2 node
cluster.
Before the upgrade process both nodes are using CentOS 6.3, corosync
1.4.1-7 and pacemaker-1.1.7.
I followed the rolling upgrade process, so I stopped pacemaker and then
corosync on node1 and upgraded to
