I'm attempting to set up a master/slave database cluster where the master is
R/W and the slave is R/O. The master failure scenario works fine (slave
becomes master, master vip moves over)however when the slave resource
goes down I want the slave vip to move to the master and then move back whe
On Aug 26, 2011, at 2:24 PM, Michael Schwartzkopff wrote:
> Hi,
>
> I set up HA NFS Server according to the HOWTO from linbit. Basically it is a
> clone of the NFS server and a clone of the root filesystem. A group of the
> Filesystem, the exportfs and the ip address depends on a DRBD and the
Hi,
I set up HA NFS Server according to the HOWTO from linbit. Basically it is a
clone of the NFS server and a clone of the root filesystem. A group of the
Filesystem, the exportfs and the ip address depends on a DRBD and the root-
exportfs clone.
See below for the configuration.
Lets say, the
I'm having a problem with master/slave promotion using the most recent
version of the mysql ocf script hosted off the clusterLabs/resource-agents
github repo.
The script works well failing over to a slave if a master looses connection
with the cluster. However, when the master rejoins the cluster
On 08/24/11 17:38, Vladislav Bogdanov wrote:
> 23.08.2011 12:19, Gao,Yan wrote:
> [snip]
>> When allocating every resource, we compare the capacity of the nodes.
>> The node has more remaining capacity is preferred. This would be quite
>> clear if we only define one kind of "capacity". While if we
Ladies and Gentlemen,
Pacemaker 1.1.5 has just hit Debian GNU/Linux Unstable ("Sid") along with
according versions of corosync (1.4.1), cluster-glue (1.0.7+hg),
resource-agents (3.9.2) and Heartbeat (3.0.5).
I have also prepared Backports for Debian GNU/Linux 6.0 ("Squeeze") but can
not upload t
