[
https://issues.redhat.com/browse/JGRP-2486?page=com.atlassian.jira.plugin...
]
Bela Ban commented on JGRP-2486:
--------------------------------
As I mentioned on the PR, it is not a good idea to fix something downstream (4.0.22
branch). I suggest you also create a PR for the 4.x branch.
I've accepted the PR, but this is the last time I've accepted a downstream PR...
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
Fix For: 4.0.24
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)