-
Notifications
You must be signed in to change notification settings - Fork 14
Add generic distributed coordination operations #141
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
Conversation
csegarragonz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mainly two design concerns/questions I have, rather than objections on the implementation:
- Would it be possible to have a per-application
DistributedCoordinationinstance? - Do we want to add timeouts to distributed coordination operations to prevent deadlocks?
Happy to discuss this offline
| Flush = 2, | ||
| Unregister = 3, | ||
| GetResources = 4, | ||
| SetThreadResult = 5, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that SetThreadResult is no longer used.
|
Pretty much rewritten now so moved to a fresh PR: #161 |
Rewritten in #161