Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.0.1.CR1, 7.0.1.GA
Affects Version/s: 7.0.0.GA
Component/s: None
Labels:
- testsuite_stability

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.0.z.GA
Git Pull Request:
https://github.com/infinispan/infinispan/pull/4024

Sprint:
EAP 7.0.1

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

If the joiner has the correct view id, but the current status is
RECOVERING_CLUSTER, we should wait for the cluster status recovery to
finish before adding the new member.

We are currently not doing that, so the new member could be erased by the status recovery process that's in progress. This can happen if the coordinator joiner already had been a member of the JGroups cluster for some time, and there's no view change when they actually start their caches (exactly the scenario in ConcurrentStartTest).

causes

ISPN-5495 ConcurrentStartTest.testConcurrentStart random failures

Closed

clones

ISPN-6235 ClusterTopologyManagerImpl join during cluster status recovery

Closed

is incorporated by

ISPN-6433 Backport to 8.1.x branch

Closed

JBEAP-4124 Upgrade to Infinispan 8.1.4.Final

Closed

Assignee:: Dan Berindei (Inactive)

Reporter:: Brad Maxwell

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2016/05/18 8:13 PM

Updated:: 2020/09/30 2:54 PM

Resolved:: 2016/05/18 8:26 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates