Bug 1278478

Summary: totemconfig: Make sure join timeout is less than consensus
Product: Red Hat Enterprise Linux 6 Reporter: Jan Friesse <jfriesse>
Component: corosyncAssignee: Jan Friesse <jfriesse>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: low Docs Contact:
Priority: low    
Version: 6.8CC: ccaulfie, cluster-maint, jkortus
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: corosync-1.4.7-3.el6 Doc Type: Bug Fix
Doc Text:
No doc text needed.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-10 19:42:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Proposed patch
none
Proposed patch 2 none

Description Jan Friesse 2015-11-05 15:03:32 UTC
Created attachment 1090140 [details]
Proposed patch

Description of problem:
The thesis contains this paragraph:

  "The Join timeout is shorter than the Consensus timeout and is used
   to increase the probability that Join messages from all currently
   working processors are received during a single round of
   consensus."

Empirically I can confirm that making join less than consensus can
cause havoc with a cluster so I think we should enforce this.


Version-Release number of selected component (if applicable):
1.4.7

Expected results:
Set consensus timeout < join_timeout result is
"The consensus timeout parameter (X ms) may not be less than join timeout (X ms)"

Additional info:
This is change in coroparse which is not used directly when using cman, so this is SanityOnly.

Comment 1 Jan Friesse 2015-11-05 15:06:07 UTC
Created attachment 1090141 [details]
Proposed patch 2

config: Fix 'then' for 'than' typos in messages and some comments.

Also fix a 'delier' for 'deliver', which I only spotted because the line
had a (correct) 'then' on it!

Comment 6 errata-xmlrpc 2016-05-10 19:42:54 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-2016-0753.html