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

handle case of same service ID on different nodes #135

Merged
merged 1 commit into from
May 31, 2022
Merged

Conversation

eikenb
Copy link
Contributor

@eikenb eikenb commented May 31, 2022

Duplicate service ID on 2 nodes would end up with only 1 service being
deregistered (from being a service in good standing), leaving the
service with the duplicate ID registered.

This includes the node's name in the id to make sure services have
a unique ID across nodes.

Alternative to #131 using a struct instead of a 2-d map.
Fixes #131

Duplicate service ID on 2 nodes would end up with only 1 service being
deregistered (from being a service in good standing), leaving the
service with the duplicate ID registered.

This includes the node's name in the id to make sure services have
a unique ID across nodes.
@eikenb eikenb added the bug label May 31, 2022
@eikenb eikenb added this to the v0.6.1 milestone May 31, 2022
@eikenb eikenb requested a review from a team May 31, 2022 20:15
Copy link
Member

@lornasong lornasong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes sense to me!

@eikenb eikenb merged commit 33dfa54 into main May 31, 2022
@eikenb eikenb deleted the duplicate-service-id branch May 31, 2022 22:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants