uot;rsc_defaults-options"
>
> You may want to enable resource-stickiness to avoid resources shuffling
> around needlessly.
>
>
What is the use of default_resource-stickness value(If in case of we have
defined resource-stickiness value to all primitive resources)?? As I have
alr
esource-stickiness to avoid resources shuffling
> around needlessly.
>
>
What is the use of default_resource-stickness value(If in case of we have
defined resource-stickiness value to all primitive resources)?? As I have
already defined the resource_stickiness value to my all p
Hello All,
Thanks for suggesting me to upgrade from heartbeat-2.1.3 to pacemaker +
heartbeat..
Now the things seems to be so fine..but still I have some doubts. It will be
very grateful to get those doubts cleared..
I've got a 3 node cluster of OpenVZ (running VM's managed by pacemaker with
Hear
Hello,
Hi,
On Tue, Jan 05, 2010 at 07:54:30PM +0530, jaspal singla wrote:
> Hello,
>
> I have 3 nodes cluster with 2 active and 1 passive nodes.
>
> I have configured 2 resources groups containing all necessary file system,
> ip address and vz-script.
>
> My cluster
Hello,
I have 3 nodes cluster with 2 active and 1 passive nodes.
I have configured 2 resources groups containing all necessary file system,
ip address and vz-script.
My cluster works perfect if both of Active nodes fail there resources one at
a time to passive node but the issue which I am facin
Hello All,
I am getting a strange issue while configuring 3 node clustering..
The issue is I have successfully deployed 2 node Active-passive cluster for
the Virtozzo with shared iSCSI.
Problem:
Now I have a requirement for 3 node clusetring with 2 Active and 1 passive
node. But when I try to ad