Bug 647291 - if a node originates more then 512 messages in recovery it will sigabort (assert)
Summary: if a node originates more then 512 messages in recovery it will sigabort (ass...
Keywords:
Status: CLOSED DUPLICATE of bug 588898
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: openais
Version: 5.5
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Steven Dake
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On: 588500
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-27 19:55 UTC by Benjamin Kahn
Modified: 2016-04-26 13:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2010-12-21 07:11:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
patch to fix problem (620 bytes, patch)
2010-12-21 07:09 UTC, Steven Dake 		no flags Details | Diff
View All

Description Benjamin Kahn 2010-10-27 19:55:05 UTC 
This bug has been copied from bug #588500 and has been proposed
to be backported to 5.4 z-stream (EUS).
Comment 3 Steven Dake 2010-12-21 07:09:59 UTC 
Created attachment 469920 [details]
patch to fix problem
Comment 4 Steven Dake 2010-12-21 07:11:46 UTC 

*** This bug has been marked as a duplicate of bug 588898 ***
Comment 5 Douglas Silas 2011-01-11 23:16:50 UTC 
    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.
    
    New Contents:
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.
Note You need to log in before you can comment on or make changes to this bug.