On Fri, 2018-06-01 at 22:58 +0800, Confidential Company wrote:
> Hi,
>
> I have two-node active/passive setup. My goal is to failover a
> resource once a Node goes down with minimal downtime as possible.
> Based on my testing, when Node1 goes down it failover to Node2. If
> Node1 goes up after
Hi,
I have two-node active/passive setup. My goal is to failover a resource
once a Node goes down with minimal downtime as possible. Based on my
testing, when Node1 goes down it failover to Node2. If Node1 goes up after
link reconnection (reconnect physical cable), resource failback to Node1
even
Hi,
I have two node active/passive setup. This is my configuration:
#service firewalld stop
#vi /etc/hosts --> 192.168.2.121 (Node1) / 192.168.2.122 (Node2)
- Private Network (Direct connect)
#systemctl start pcsd.service
#systemctl enable pcsd.service
#passwd hacluster --> define pw
On Fri, 2018-06-01 at 11:15 +0300, Michael Kolomiets wrote:
> Hi
> I have asymmetric cluster. After upgrade pacemaker to version 1.1.18
> I tried to use "resource-discovery=exclusive" attr to limit probes
> when resources (VirtualDomain) start.
> But I dont see records in log on nodes where
Hi
I have asymmetric cluster. After upgrade pacemaker to version 1.1.18 I
tried to use "resource-discovery=exclusive" attr to limit probes when
resources (VirtualDomain) start.
But I dont see records in log on nodes where cluster does probes before
start resource. Moreover, I have run the guest
On Fri, Jun 1, 2018 at 12:22 AM, Casey & Gina wrote:
>
>> pacemaker is too old. The error most likely comes from missing
>> OCF_RESKEY_crm_feature_set which is exported by crm_resource starting
>> with 1.1.17. I am not that familiar with debian packaging, but I'd
>> expect resource-agents-paf
