RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1059607 - [RFE] Make auto_tie_breaker node configurable
Summary: [RFE] Make auto_tie_breaker node configurable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: corosync
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Christine Caulfield
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 1129722
TreeView+ depends on / blocked
 
Reported: 2014-01-30 09:14 UTC by Christine Caulfield
Modified: 2015-03-05 08:26 UTC (History)
8 users (show)

Fixed In Version: corosync-2.3.3-3.el7
Doc Type: Release Note
Doc Text:
Corosync Tie Breaker Enhancement The auto_tie_breaker quorum feature of Corosync has been enhanced to provide options for more flexible configuration and modification of tie breaker nodes. Users can now select a list of nodes that will retain quorum in case of an even cluster split, or choose that quorum will be retained by the node with the lowest node ID or the highest node ID.
Clone Of:
: 1129722 (view as bug list)
Environment:
Last Closed: 2015-03-05 08:26:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Free object allocated at quorum_register_callback (1.02 KB, patch)
2014-06-12 07:03 UTC, Jan Friesse 		no flags Details | Diff
votequorum: Add extended options to auto_tie_breaker (11.78 KB, patch)
2014-06-12 07:03 UTC, Jan Friesse 		no flags Details | Diff
votequorum: Properly initialize atb and atb_string (1.01 KB, patch)
2014-06-12 07:36 UTC, Jan Friesse 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0365 0 normal SHIPPED_LIVE corosync bug fix and enhancement update 2015-03-05 12:51:37 UTC

Description Christine Caulfield 2014-01-30 09:14:09 UTC 
Corosync's votequorum subsystem has an auto-tie-breaker feature that, in the event of a network split, will use the lowest node ID to decide which partition retains quorum.

This needs to be more configurable to give users better control over which node survives the split.

At it's simplest level this could just be nominating a node (or a hierarchy of nodes) that can be used to hold quorum. Also useful might be the pacemaker DC election idea of using the node that has been in the cluster longest (the most stable node).

Feel free to add other ideas to the bug.
Comment 2 Christine Caulfield 2014-02-21 09:42:03 UTC 
commit 90d448af3b4b4508ca890cce67113cb226475d3b
Author: Christine Caulfield <ccaulfie>
Date:   Mon Feb 17 16:29:45 2014 +0000

    votequorum: Add extended options to auto_tie_breaker
Comment 5 Jan Friesse 2014-06-12 07:03:13 UTC 
Created attachment 907961 [details]
Free object allocated at quorum_register_callback

Free object allocated at quorum_register_callback

Memory object allocated with malloc at quorum_register_callback
is not freed. The object is linked to internal_trackers_list.

The object is unlinked at quorum_unregister_callback. However,
it is not freed at the function.

Signed-off-by: Masatake YAMATO <yamato>
Reviewed-by: Jan Friesse <jfriesse>
Comment 6 Jan Friesse 2014-06-12 07:03:51 UTC 
Created attachment 907962 [details]
votequorum: Add extended options to auto_tie_breaker

votequorum: Add extended options to auto_tie_breaker

This patch adds more flexibility to the auto_tie_breaker feature of
votequorum. With this, not only can the lowest nodeid be used as
a tie breaker, but also the highest, or a node from a nominated list.

If there is a list of nodes, the first node in the list that was not
part of the previous partition is used. This allows the user to
specify a preferred set of nodes but prevents a split-brain if the
cluster divides evenly with a node in each half.

Signed-off-by: Christine Caulfield <ccaulfie>
Reviewed-by: Jan Friesse <jfriesse>
Comment 7 Jan Friesse 2014-06-12 07:36:12 UTC 
Created attachment 907986 [details]
votequorum: Properly initialize atb and atb_string

votequorum: Properly initialize atb and atb_string

icmap_get_* behavior is to NOT modify passed variable when it doesn't
success. So we must initialize variable before icmap_get_* call.

Signed-off-by: Jan Friesse <jfriesse>
Reviewed-by: Fabio M. Di Nitto <fdinitto>
Comment 12 Jiri Herrmann 2014-12-12 15:32:20 UTC 
If this Feature should be included in the 7.1 Release Notes, could you please change the Doc Type from Enhancement to "Release Note"?

Note that the Release Notes are intended to list the most prominent and customer-relevant new features rather than every single enhancement.

Cheers,
Jirka
Comment 15 errata-xmlrpc 2015-03-05 08:26:37 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0365.html
Note You need to log in before you can comment on or make changes to this bug.