Hi Ondrej,
Yes, you are right. This issue was specific to floating IPs, not with local
IPs.
Post becoming master, I was sending "Neighbor Advertisement" message for my
floating IPs. This was a raw message which was created by me, so I was the
one who was setting flags in it.
Please find attached
Hi,
I'm playing with a test 3 node cluster - two clustered node and one remote node.
Tried my config on Centos 7.4 and Fedora 29 with
pacemaker-1.1.19,corosync-2.4.3-4,resource-agents-4.1.1 and
pacemaker-2.0.0-4,corosync-3.0.1-1,resource-agents-4.2.0-1.
My problem is when remote node3 is fenced
Sven,
Hi,
we were running a corosync config including 2 Rings for about 2.5 years on a two node NFS Cluster (active/passive). The first ring (ring 0) is configured on a dedicated NIC for Cluster internal communications. The second ring (ring 1) was configured in the interface where the NFS
On Mon, 2019-04-08 at 13:37 +0100, Leonardo Assunção wrote:
> Hi,
>
> I have two machines with the same characteristics:
> Centos7.6;
> pcs 0.9.165;
> Pacemaker 1.1.19-8.el7_6.4;
> Corosync 2.4.3;
>
> In the cluster, i setup an ip and a service, if a node fails the
> service goes with the ip.
On 4/5/19 8:18 PM, Rohit Saini wrote:
*Further update on this:*
This issue is resolved now. ILO was discarding "Neighbor Advertisement"
(NA) as Solicited flag was set in NA message. Hence it was not updating
its local neighbor table.
As per RFC, Solicited flag should be set only in NA message
Hi,
I have two machines with the same characteristics:
Centos7.6;
pcs 0.9.165;
Pacemaker 1.1.19-8.el7_6.4;
Corosync 2.4.3;
In the cluster, i setup an ip and a service, if a node fails the service
goes with the ip.
Why does the service restart? when node2 joins the cluster, after
On 2019-04-07T12:06:40, Andrei Borzenkov wrote:
> After reading sources and experimenting I still do not see how it can
> help in two node cluster. In this case SBD will assume both nodes are
> out of quorum and both nodes will commit suicide.
It helps by not making a single SBD device a single
