-
Notifications
You must be signed in to change notification settings - Fork 75
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
No TieBreaker added in case of it's absence #361
Comments
Hello, Logs
Please note the
during Also you might want to check
If you can reproduce your issue, please add the needed steps as well as the version of the Linstor controller. |
Hi,
Now whatever I do, I can't get it to create TieBreakers on B. I tried toggling auto-add-quorum-tiebreaker on the controller off then on but that didn't fix it. That property does not exist on the resources themselves however, maybe that's the issue ? Presumably evacuating one node in a 3 node cluster counts as actively deleting it ? Is there a way to get linstor to re-evaluate and create the missing tie breakers now without needing to re-create the resources ? |
Hi, case 1:
case 2:
(XOSTOR specific) case 3:
I have noticed that if I re-enable automatic tiebreakers on a resource, that new tiebreakers are created (even if the drbd option for auto tiebreakers was never set to False on the resource definition). I use this workaround now:
Now while I think this workaround is a method to, in a way, re-evaluate the tiebreakers, it's likely not viable for many use-cases. I hope it can be of some use to uncover the root cause though or as a stopgap solution for someone with a similar use-case. Linstor version: |
If there is not enough online nodes in cluster, no TieBreaker created for resources with replica factor 2.
If no TieBreaker, in this case (or it wasn't created because any other reason) Linstor won't create TieBreaker in future.
Herewith, if I look advices, I see that there is problem
linstor r advice: Resource has 2 replicas but no tie-breaker, could lead to split brain
The text was updated successfully, but these errors were encountered: