[
https://issues.jboss.org/browse/JGRP-2387?page=com.atlassian.jira.plugin....
]
Dennis Reed commented on JGRP-2387:
-----------------------------------
Two potential solutions:
- verify the node is a cluster member before adding an entry to timestamps.
- add to timestamps, but then when sending a suspect event verify it's a member of the
cluster. If not, remove from timestamps and ignore.
(this one may be lower impact than checking on every message)
Message from a non-member causes FD_ALL to continually suspect it
-----------------------------------------------------------------
Key: JGRP-2387
URL:
https://issues.jboss.org/browse/JGRP-2387
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Dennis Reed
Assignee: Bela Ban
Priority: Major
If a FD_SOCK control message from a non-member is seen by FD_SOCK, it will start
continually suspecting that node. If msg_counts_as_heartbeat=true then any message from a
non-member triggers the issue. The issue is cleared on the next view change.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)