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

Implement lock operation idempotence for client #8359

Closed
GhostInAMachine opened this issue Jun 10, 2016 · 3 comments

Comments

Projects
None yet
4 participants
@GhostInAMachine
Copy link

commented Jun 10, 2016

Call reference IDs are included in Lock operations issued from member to member to prevent double locking when lock operation is retried. Client lock requests do not have these.

@asimarslan

This comment has been minimized.

Copy link
Member

commented Jun 13, 2016

The solution is to add a new field "reference call Id" to all lock messages which mimics the reference call id field on AbstractLockOperation.

This fix does change client protocol but as only a field is added there is no compatibility problem

@asimarslan asimarslan added this to the 3.7 milestone Jun 13, 2016

@asimarslan

This comment has been minimized.

Copy link
Member

commented Jun 13, 2016

related to #5602

@ihsandemir

This comment has been minimized.

Copy link
Contributor

commented Jul 21, 2016

Closing the issue since the implementation is completed.

@ihsandemir ihsandemir closed this Jul 21, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.