[jboss-jira] [JBoss JIRA] (JGRP-1743) NAKACK*: log a warning if xmit_table gets large

[Bela Ban (JIRA)]

     [ https://issues.jboss.org/browse/JGRP-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban resolved JGRP-1743.
----------------------------

    Resolution: Rejected


I'm afraid I'll have to reject this for the following reasons:
- Setting a threshold to trigger a warning is almost always wrong: either the warning never triggers if the threshold is too high or it always triggers it the threshold is too low
- There may be cases where NAKACK2 storing 1 million (small) messages is perfectly valid
- I don't think this is JGroups functionality, but management functionality, e.g. this could be done by periodically running a JMX/probe operation to fetch the number of messages (or total size) in all cluster nodes
                
> NAKACK*: log a warning if xmit_table gets large
> -----------------------------------------------
>
>                 Key: JGRP-1743
>                 URL: https://issues.jboss.org/browse/JGRP-1743
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 3.4.1
>            Reporter: Dennis Reed
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 3.5
>
>
> There have been some cases where NAKACK* accumulates large number of messages, causing OutOfMemoryErrors.
> Large numbers of messages in NAKACK* would almost always indicate a problem, which the user should be aware of.
> Logging a warning if the number of messages in NAKACK passes a configurable threshold would let the user investigate and take action sooner before a catastrophic OutOfMemoryError, or other issues occur.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira