[Pacemaker] New action for resource running in multiple nodes

Arnold Krille arnold at arnoldarts.de
Mon Aug 12 18:35:08 EDT 2013

On Mon, 12 Aug 2013 19:27:33 +0200 Adrián López Tejedor
<adrianlzt at gmail.com> 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 in the service network, but
> networks are virtualized, so maybe the problem persists.
> And of course, we don't have stonith. It is the same problem, I have
> no control over the VMWare hosts, and seems that they have to pay an
> extra to use the API needed by the stonith plugin.
> Meanwhile, I try to find
> Probably this two problems will be fixed in a couple of months, but
> meanwhile I have try to maintain the cluster up :)

Sounds a bit as if the hardware-layer has bridging with stp featuring
some seconds of unavailability.

You could try to increase the corosyncs parameters concerning
communication timeouts.

Good luck,

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130813/f7ba54bc/attachment-0003.sig>

More information about the Pacemaker mailing list