[TRACKING ISSUE] Handle membership in the client on split brain [API-2077] #387
Labels
Jira
Creates a corresp. Jira issue in the APIs project.
Source: Tracking
Originated from the Tracking bot.
Comments
github-actions
bot
changed the title
|
Internal Jira issue: API-2077 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The tracking issue for the Java side PR.
Handle membership in the client on split brain
See hazelcast/hazelcast#17147 for details.
It could be the case that when split brain occurs the member list
version that client remembers is already bigger than the the
half that client is connected to. In this case, client can not
apply the member list because it has an older version. But
in fact, it should have been applied, otherwise client get
stuck with an old member-list.
As a solution, we clear the member-list version everytime
we re-register the member list listener.
fixes hazelcast/hazelcast#16855
The text was updated successfully, but these errors were encountered: