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

Conflicts not detected after initial registration #1356

Open
bdraco opened this issue Feb 5, 2024 · 0 comments
Open

Conflicts not detected after initial registration #1356

bdraco opened this issue Feb 5, 2024 · 0 comments

Comments

@bdraco
Copy link
Member

bdraco commented Feb 5, 2024

If we register a service and the network is offline (ie plugged in later) or dropping packets, we won't know that another host is using the name. We need late conflict detection.

When we detect a conflict we need to go through election again and mutate the ServiceRegistry with the new name

https://datatracker.ietf.org/doc/html/rfc6762#section-9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant