[
https://issues.jboss.org/browse/JGRP-2387?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-2387:
--------------------------------
{quote}
This triggers VERIFY_SUSPECT to try to ping it, which it can't because it doesn't
have the address (but can cause a "no physical address" log in some cases).
{quote}
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_, its address should still be in the cache! The cache only removes
'removable' elements when UDP.logical_addr_cache_max_size (default=2000) has been
exceeded, but this should not be the case! Or does JDG set this value by default?
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)