[jboss-jira] [JBoss JIRA] (JGRP-2486) FD Monitor get stuck on TrasferQueueBundler

[Bela Ban (Jira)]

    [ https://issues.redhat.com/browse/JGRP-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177916#comment-14177916 ] 

Bela Ban commented on JGRP-2486:
--------------------------------

This wouldn't happen if you used {{UDP}} or {{TCP_NIO2}}. Also, if you disabled the NIC, TCP itself would block after a while, so what's the use case here?

Note that you could use {{RED}} to drop messages if the queue starts getting full...

> FD Monitor get stuck on TrasferQueueBundler
> -------------------------------------------
>
>                 Key: JGRP-2486
>                 URL: https://issues.redhat.com/browse/JGRP-2486
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 4.0.22
>            Reporter: lukas brandl
>            Assignee: Bela Ban
>            Priority: Major
>         Attachments: Main.java, stack-trace.txt
>
>
> Apparently there is an issue in the FD protocol. When a cluster nodes is disconnected and the disconnect isn't handled by FD_SOCK, FD stops sending heartbeats after a while. This only happens when the queue of the TrasferQueueBundler fills up before the node is suspected.
> The stack trace shows that the FD$Monitor is blocked by the bundler. This is probably the reason why the heartbeat timeouts are not noticed.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)