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.

Sign up for GitHub

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

Jump to bottom

Implement locking support in peer discovery #1257

Closed
dcorbacho opened this issue Jun 8, 2017 · 2 comments
Closed

Implement locking support in peer discovery #1257

dcorbacho opened this issue Jun 8, 2017 · 2 comments
Assignees
@dcorbacho @kjnilsson
Labels
effort-medium enhancement
Milestone
3.7.0

Comments

@dcorbacho
Copy link
Contributor

Originally part of the rabbitmq_autocluster plugin: rabbitmq/rabbitmq-autocluster#6
@dcorbacho dcorbacho changed the title Implement lock support in peer discovery Implement locking support in peer discovery Jun 8, 2017
@dcorbacho dcorbacho added this to the 3.7.0 milestone Jun 8, 2017
@michaelklishin
Copy link
Member

effort-medium seems reasonable here because this involves 3 different engineers, multiple plugins and quite a bit of testing (on top of what's already been done in rabbitmq/rabbitmq-autocluster#6).

This was referenced Jun 9, 2017
Merged
Merged
Merged
Merged
@kjnilsson kjnilsson mentioned this issue Jun 12, 2017
Merged
@michaelklishin
Copy link
Member

There is no PR for rabbitmq-common where peer_discovery_backend resides.

This was referenced Jun 12, 2017
Merged
Merged
@dcorbacho dcorbacho mentioned this issue Jun 15, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dcorbacho dcorbacho

@kjnilsson kjnilsson

Labels
effort-medium enhancement
Projects
None yet
Milestone
3.7.0
Development

No branches or pull requests
3 participants
@michaelklishin @dcorbacho @kjnilsson