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

Reuse Room IDs when first server in the list changes #149

Open
fredo opened this issue Apr 15, 2020 · 0 comments
Open

Reuse Room IDs when first server in the list changes #149

fredo opened this issue Apr 15, 2020 · 0 comments

Comments

@fredo
Copy link
Contributor

fredo commented Apr 15, 2020

Problem Description

When the known servers list changes such that the first server in the list is removed, the new first server will become the sync point for broadcast rooms for the rest of the list. Currently, this instance will create new rooms with fresh room ids and repoints the aliases to it. This causes an interval where servers are in different broadcast rooms and therefore out of sync. This was discovered during the testing phase for the new release.
This period of Raiden nodes not working correctly can be completely avoided if the new first server simply renames the alias for the broadcast rooms and reuse the room_ids. It should be a simple fix and remove all friction for this specific case which should happen rarely anyway.

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