Red Hat Bugzilla – Bug 588500
if a node originates more then 512 messages in recovery it will sigabort (assert)
Last modified: 2016-04-26 09:38:37 EDT
Description of problem:
The queue length is not long enough for really high loss networks resulting in sigabort. Instead of 512 entries, it should be the max entries allowed which is 16384 entries.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create 95% loss in multicast packets
2. start 8 node cpgverify operation
3. kill 1 node
sigabort of some nodes
Created attachment 411114 [details]
patch to fix the problem
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
In high-loss networks, an assert based on a constant value for the retransmit message queue size could have caused a some nodes to receive SIGABRT signals, and therefore terminate. This constant value has been increased to correspond to the maximum number of entries, thus resolving the issue.
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 therefore 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.