[jboss-jira] [JBoss JIRA] (JGRP-2387) Message from a non-member causes FD_ALL to continually suspect it
[
https://issues.jboss.org/browse/JGRP-2387?page=com.atlassian.jira.plugin....
]
Dennis Reed edited comment on JGRP-2387 at 10/3/19 11:34 AM:
-------------------------------------------------------------
I'm wondering why the logical address cache in the transport
would not have the address: unless the
member to which we're trying to send the message has never been a member
TP.java:handleDownEvent, case VIEW_CHANGE:
// fix for https://jira.jboss.org/jira/browse/JGRP-918
logical_addr_cache.retainAll(members);
So I had assumed this was expected. But now I see that's not a real map, and
doesn't actually remove them.
was (Author: dereed):
I'm wondering why the logical address cache in the transport
would not have the address: unless the
member to which we're trying to send the message has never been a member
TP.java:handleDownEvent, case VIEW_CHANGE:
// fix for https://jira.jboss.org/jira/browse/JGRP-918
logical_addr_cache.retainAll(members);
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
Fix For: 4.1.6
Attachments: Test.java
If an FD_ALL control message from a non-member is seen by FD_ALL, 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 does not cause any functional issues in the cluster, but can cause repeated WARN
logs in some cases.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)