[
https://issues.jboss.org/browse/JGRP-2387?page=com.atlassian.jira.plugin....
]
Dennis Reed commented on JGRP-2387:
-----------------------------------
Workaround to make the warnings go away:
This would apply to the "no physical address" logs, but not the FD_ALL warnings
(which only existed in a few versions).
The FD_ALL log was increased to WARN in
commit da67b146b55964cf168c73625d77cbdc66390d06
Author: Bela Ban <belaban(a)yahoo.com>
Date: Mon Jan 30 14:18:55 2017 +0100
FD_ALL / FD_SOCK: changed suspected peer log stmt from DEBUG -> WARN
But was overwritten by a later merge:
commit 89b5ea49a46946a08f9f4642641b2726683e5218
Date: Fri Aug 4 17:42:52 2017 +0200
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, bla6.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)