On 13/08/2013, at 2:57 AM, Andreas Mock wrote:
> Hi Adrián,
>
> IMHO the effort would focus on the wrong issue.
> Make your network for clustering reliable. It is THE building block
> of a cluster besides the nodes.
> - Additional network cards
> - Different vendor
> - Bonding
> - Different pa
On Mon, 12 Aug 2013 19:27:33 +0200 Adrián López Tejedor
wrote:
> The problem is the network is out of my control. All the nodes are
> virtual machines over some VMWare ESX.
> We have two different networks, one for the service, and the other
> for the cluster.
> One idea is to create a second ring
Hi Andreas,
The problem is the network is out of my control. All the nodes are virtual
machines over some VMWare ESX.
We have two different networks, one for the service, and the other for the
cluster.
One idea is to create a second ring in the service network, but networks
are virtualized, so may
Hi Adrián,
IMHO the effort would focus on the wrong issue.
Make your network for clustering reliable. It is THE building block
of a cluster besides the nodes.
- Additional network cards
- Different vendor
- Bonding
- Different path through switches
On a two-node-cluster without the ne
Hi!
In the environment we use corosync/pacemaker, recently we are having some
problems with the network used to maintain the cluster. This short
interruptions cause the passive node (we have a two node active-passive
configuration with apache tomcat) to think he is alone, and start another
instanc
Sorry, didn't send this to the list...
- Forwarded message from "ge...@riseup.net" -
Date: Sun, 11 Aug 2013 18:26:44 +0200
From: "ge...@riseup.net"
To: Digimer
Subject: Re: [Pacemaker] Problem with one drbd dual primary ressource
User-Agent: Mutt/1.5.21 (2010-09-15)
Hi again,
Accordi
Sorry, didn't send this to the list...
- Forwarded message from "ge...@riseup.net" -
Date: Sun, 11 Aug 2013 17:13:25 +0200
From: "ge...@riseup.net"
To: Digimer
Subject: Re: [Pacemaker] Problem with one drbd dual primary ressource
User-Agent: Mutt/1.5.21 (2010-09-15)
Hi,
On 13-08-10 2
Hi,
I tried it with the current head beekhof/pacemaker and everything seems
to work fine.
Thanks for the fixes.
gr.
Johan
On 07-08-13 05:51, Andrew Beekhof wrote:
I believe this patch should help:
https://github.com/beekhof/pacemaker/commit/7a0a6f8
Can you give it a try?
On 07/08/20
