[ISPN-6235] ClusterTopologyManagerImpl join during cluster status recovery

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 8.2.0.CR1, 8.1.4.Final
Affects Version/s: 8.1.3.Final
Component/s: None
Labels:
- testsuite_stability

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

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

is cloned by

JBEAP-4618 ClusterTopologyManagerImpl join during cluster status recovery

Closed

is incorporated by

ISPN-6433 Backport to 8.1.x branch

Closed

There are no comments yet on this issue.

Assignee:: Dan Berindei (Inactive)

Reporter:: Dan Berindei (Inactive)

Archiver:: Amol Dongare

Created:: 2016/02/19 5:59 AM

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

Resolved:: 2016/03/01 10:39 AM

Archived:: 2024/11/28 6:21 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates

PagerDuty