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

Lock operations get timeout exception when member dies #13551

Closed
sancar opened this issue Aug 9, 2018 · 0 comments
Closed

Lock operations get timeout exception when member dies #13551

sancar opened this issue Aug 9, 2018 · 0 comments

Comments

@sancar
Copy link
Member

@sancar sancar commented Aug 9, 2018

When a client waiting for a lock to be released more than invocation timeout seconds, and the member dies, clients get operation timeout exception rather than it is redirected to another member.

@sancar sancar added this to the 3.10.5 milestone Aug 9, 2018
@sancar sancar self-assigned this Aug 9, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Aug 9, 2018
When a client waiting on lock to get it, if the member that it
is waiting on shuts down/terminated , client retries it on new
owner of the lock.

If a client waits for longer than client.invocation.timeout.seconds,
when exception came from server, it is wrapped inside
OperationTimeoutException and thrown to user.
This pr changes this behaviour so that waiting lock operations
(map.lock/trylock lock.lock/trylock condition.await) operations will
not throw OperationTimeoutException but retry the operation.

fixes hazelcast#13551
sancar added a commit to sancar/hazelcast that referenced this issue Aug 9, 2018
When a client waiting on lock to get it, if the member that it
is waiting on shuts down/terminated , client retries it on new
owner of the lock.

If a client waits for longer than client.invocation.timeout.seconds,
when exception came from server, it is wrapped inside
OperationTimeoutException and thrown to user.
This pr changes this behaviour so that waiting lock operations
(map.lock/trylock lock.lock/trylock condition.await) operations will
not throw OperationTimeoutException but retry the operation.

fixes hazelcast#13551

(cherry picked from commit 79fac3c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

2 participants