pcs resource create.
Regards,
Ashutosh
On Sat, 2018-03-17 at 15:35 +0530, ashutosh tiwari wrote:
> Hi,
>
>
> We have two node active/standby cluster with a dummy? Stateful
> resource (pacemaker/Stateful).
>
> We observed that in case one node is up with master resource and
> o
Hi,
We have two node active/standby cluster with a dummy Stateful resource
(pacemaker/Stateful).
We observed that in case one node is up with master resource and other node
is booted up, state file for dummy resource is not created on the node
coming up.
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Users digest..."
>
>
> Today's Topics:
>
>1. corosync taking almost 30 secs to detect node failure in case
> of kernel panic (ashutosh tiwari)
>2. Ant
msecs.
Please let us know in case there is any more configuration controlling
membership detection.
s/w versions.
centos 6.7
corosync-1.4.7-5.el6.x86_64
pacemaker-1.1.14-8.el6.x86_64
Thanks and Regards,
Ashutosh Tiwari
___
Users mailing list: Users
v 2017 09:49:20 -0600
> From: Ken Gaillot <kgail...@redhat.com>
> To: Cluster Labs - All topics related to open-source clustering
> welcomed<users@clusterlabs.org>
> Subject: Re: [ClusterLabs] issues with pacemaker daemonization
> Message-ID: <1510242
afaik.
Do we expect it to be managed by init.d (centos 6) or pacemaker binary.
pacemaker version: *pacemaker-1.1.14-8.el6_8.1.x86_64*
Thanks and Regards,
Ashutosh Tiwari
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailma
On 06/09/2017 07:43 AM, ashutosh tiwari wrote:
> Hi,
>
> We have two node cluster(ACTIVE/STANDBY).
> Recently we moved these nodes to KVM.
>
> When we create a private virtual network and use this vnet for
> assigning cluster interfaces then things work as expected and both
Hi,
We have two node cluster(ACTIVE/STANDBY).
Recently we moved these nodes to KVM.
When we create a private virtual network and use this vnet for assigning
cluster interfaces then things work as expected and both the nodes are able
to form the cluster.
Nodes are not able to form cluster when
Hi,
We are running a two node cluster(Active(X)/passive(Y)) having muliple
resources of type IpAddr2.
Running monitor operations for multiple IPAddr2 resource is actually hoging
the cpu,
as we have configured very low value for monitor interval (200 msec).
To avoid this problem ,we are trying to