Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BACKPORT] Fixed a data loss issue on lite member promotion (#17644) #17758

Merged

Conversation

petrpleshachkov
Copy link
Contributor

@petrpleshachkov petrpleshachkov commented Oct 23, 2020

Notify cluster members on lite member promotion to update
memberGroupSize. Otherwise, a data member might be not aware of other
promoted data members, and it may cause backup operations
not being issued to other data members.

Closes #17621
Backport of: #17644

Notify cluster members on lite member promotion to update
memberGroupSize. Otherwise, a data member might be not aware of other
promoted data members, and it may cause backup operations
not being issued to other data members.

Closes hazelcast#17621
@petrpleshachkov petrpleshachkov changed the title Fixed a data loss issue on lite member promotion (#17644) [BACKPORT] Fixed a data loss issue on lite member promotion (#17644) Oct 23, 2020
@mmedenjak mmedenjak added this to the 4.0.4 milestone Oct 23, 2020
@vbekiaris vbekiaris modified the milestones: 4.0.4, 3.12.11 Oct 27, 2020
thirdHazelcastInstance.getCluster().promoteLocalLiteMember();

// check if cluster is in a good shape
assertTrueEventually(new AssertTask() {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: could use waitClusterForSafeState here and assertEqualsEventually in subsequent assertTrueEventually usages below.

@hazelcast hazelcast deleted a comment Oct 28, 2020
@petrpleshachkov petrpleshachkov merged commit 8509d80 into hazelcast:3.12.z Dec 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants