Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement option to keep active partition active if all requirements are fulfilled #7

Closed
jfriesse opened this issue Jan 2, 2020 · 2 comments

Comments

@jfriesse
Copy link
Member

jfriesse commented Jan 2, 2020

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
@jfriesse
Copy link
Member Author

jfriesse commented Jun 3, 2020

This is needed also to make 2 node cluster work correctly with knet where restarted node may get quorum because creation of single node membership first. Relevant ML discussion https://lists.clusterlabs.org/pipermail/users/2020-April/027087.html

@jfriesse
Copy link
Member Author

jfriesse commented Oct 27, 2020

This issue is now fixed via fbc34f3, 09c6f78 and 7a0201a so can be closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant