Red Hat Bugzilla – Bug 135098
Some routed IP tiebreaker addresses not recognized by cluquorumd
Last modified: 2009-04-16 16:15:35 EDT
Description of problem:
In trying to reproduce another problem I had set the IP tiebreaker
address to be something with some latency. The routed address
approximately half way around the world took ~150ms. Not too bad.
A single node with allow_soft failed to acheive quorum with this address:
Oct 8 11:37:12 tng4-2 cluquorumd: <info> IPv4-TB: Pinging
Oct 8 11:37:19 tng4-2 cluquorumd: <info> IPv4-TB: No response.
Oct 8 11:37:19 tng4-2 cluquorumd: <debug> Need 1 more members
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 104950 [details]
Ping patch which fixes runt packets on 1.2.16 and 1.2.22
This has been verified as of 1.2.22.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.