[
https://issues.jboss.org/browse/JGRP-2293?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on JGRP-2293:
------------------------------------
Yes, either of these make the test work from Maven:
{code}
mping.setBindAddr(InetAddress.getByName("wlan ip"));
or
mping.setMcastAddr(InetAddress.getByName("225.5.5.5"));
{code}
I'm still baffled why the test works unchanged in IntelliJ: like I said, it uses
exactly the same bind/mcast addresses.
Graceful concurrent leaving of coordinator(s) leaves the cluster with
stale views
---------------------------------------------------------------------------------
Key: JGRP-2293
URL:
https://issues.jboss.org/browse/JGRP-2293
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.14
Reporter: Radoslav Husar
Assignee: Bela Ban
Priority: Critical
Fix For: 4.0.17
Attachments: IMG_20190123_124154.jpg
JGroups does not handle concurrent leaving of nodes correctly. This is a typical use case
in cloud environment when scaled down with an autoscaler/manually which we need to
handle.
A simple test can be devised which fails first n (where n>1) nodes from a cluster,
reproducer PR
https://github.com/belaban/JGroups/pull/397
--
This message was sent by Atlassian Jira
(v7.12.1#712002)