You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Idea is to add option which, if activated, would try to keep vote for current active partition if all other requirements are fulfilled.
Idea based on report from ML:
Hi ,
I am planning to use Corosync Qdevice version 3.0.0 with corosync version 2.4.4 and pacemaker 1.1.16 in a two node cluster.
I want to know if failback can be avoided in the below situation.
1. The pcs cluster is in split brain scenario after a network break between two nodes. But both nodes are visible and reachable from qdevice node.
2. The qdevice with ffsplit algorithm selects node with id 1 (lowest node id) and node 1 becomes quorate.
3. Now if node 1 goes down/is not reachable from qdevice node , the node 2 becomes quorate.
But when node 1 becomes again reachable from qdevice , it becomes quorate and node 2 again goes down. i.e The resources failback to node 1.
Is there any way to prevent this failback.
With Regards
Somanath Thilak J
The text was updated successfully, but these errors were encountered:
Idea is to add option which, if activated, would try to keep vote for current active partition if all other requirements are fulfilled.
Idea based on report from ML:
The text was updated successfully, but these errors were encountered: