[
https://issues.jboss.org/browse/ISPN-10575?page=com.atlassian.jira.plugin...
]
Dan Berindei commented on ISPN-10575:
-------------------------------------
The first problem I encountered was that {{TEST_PING}} allows suspending the discovery and
re-enabling it, so a test like
{{ClusterTopologyManagerTest.testClusterRecoveryWithRebalance}} can have multiple
partitions and control which partition a new node will join.
I partially implemented the functionality by subclassing {{LOCAL_PING}} and changing the
cluster name to the node address when discovery is supposed to be disabled. The remaining
issue is that {{LOCAL_PING}} doesn't update {{PingData::isCoord}} on view changes, so
after a merge a new node will always try to talk to the initial coordinator instead of the
post-merge coordinator.
Try to replace TEST_PING with LOCAL_PING
----------------------------------------
Key: ISPN-10575
URL:
https://issues.jboss.org/browse/ISPN-10575
Project: Infinispan
Issue Type: Task
Components: Core
Affects Versions: 10.0.0.CR1
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Major
Fix For: 10.0.0.Final
JGroups added a {{LOCAL_PING}} protocol (JGRP-2284) that could potentially be used to
replace our {{TEST_PING}}, so that we don't depend on {{Discovery}} internals.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)