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 614124 - [RFE] have cman print expected failure detection time based upon heuristics
Summary: [RFE] have cman print expected failure detection time based upon heuristics
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cluster
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
URL:
Whiteboard:
: 614128 (view as bug list)
Depends On: 614128
Blocks: 655920 693781
TreeView+ depends on / blocked
 
Reported: 2010-07-13 17:46 UTC by Steven Dake
Modified: 2016-04-26 14:25 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-08 17:07:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Steven Dake 2010-07-13 17:46:00 UTC 
Currently our users don't know what to expect the failure between config changes should be when considering the following factors

multipath configuration
qdisk configuration
totem configuration

Have cman print the expected failure detection time based upon heuristics.
Comment 7 Lon Hohberger 2011-05-31 22:14:31 UTC 
The goal here is to have CMAN print out a value after taking in to account all of the various timings on the system.

These timings include (but are not entirely limited to; see other bug):
  * multipath timeout
  * quorum disk timeout
  * cman (totem) timeout

This is done in conjunction with execution of heuristics as part of bug 614128  so setting a dependency.

Effectively, this feature is simply designed to print out a message stating how long, in total, the cluster should take to detect a host has died and initiate recovery.

Currently, most of the timers required are printed in the logs, with no indication of what they actually mean.

So, for example, one might see something like the following in the logs as a consequence of implementing this feature:

   corosync[5597]:   [CMAN  ] CMAN X.Y.Z (built Dec 24 2012 14:08:21) started
   corosync[5597]:   [CMAN  ] Failure recovery initiation time 11.2 seconds

If, you then went over and pulled the plug on a host in the cluster, it should be approximately 11.2 seconds before you see the following message:

   corosync[5597]:   [QUORUM] Members[1]: 1
   corosync[5597]:   [TOTEM ] A processor joined or left the membership and a new membership was formed.
   ...
Comment 9 Lon Hohberger 2011-07-21 14:21:23 UTC 
*** Bug 614128 has been marked as a duplicate of this bug. ***
Comment 12 Lon Hohberger 2011-08-08 17:05:10 UTC 
Most of the tuning and documentation has been superseded by work here:

https://access.redhat.com/knowledge/techbriefs/how-optimally-configure-quorum-disk-red-hat-enterprise-linux-clustering-and-hig
Note You need to log in before you can comment on or make changes to this bug.