[BACKPORT] Notify invocations when a member leaves in FROZEN/PASSIVE cluster state #11202
Conversation
When cluster state doesn't allow new members to join, we don't modify partition table if a member leaves. But invocations targeting that left member, blocked operations belonging to that member should be notified. Currently, those invocations doesn't get a response and fail with OperationTimeoutException.
mdogan
force-pushed the
mdogan:passive-state-member-remove-x
branch
from
3bfa8bd
to
0698550
pveentjer
changed the title
pveentjer
merged commit 683edb1
into
hazelcast:maintenance-3.x
1 check passed
1 check passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
When cluster state doesn't allow new members to join, we don't modify
partition table if a member leaves. But invocations targeting that left
member, blocked operations belonging to that member should be notified.
Currently, those invocations doesn't get a response and fail with
OperationTimeoutException.
Backport of #11201