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

Peer-to-peer RelayServer #7

Open
belaban opened this issue Nov 25, 2019 · 0 comments
Open

Peer-to-peer RelayServer #7

belaban opened this issue Nov 25, 2019 · 0 comments
Assignees
@belaban
Labels
enhancement New feature or request
Milestone
1.2

Comments

@belaban
Copy link
Member

belaban commented Nov 25, 2019 •
edited
Loading

Rather than going to a central UpgradeServer, we should have one in every UPGRADE protocol. This allows us to get rid of 1 moving part, namely the separate UpgradeServer process required in the current solution.

The UpgradeServer instance needs to discover other UpgradeServer instances in other members dynamically. Perhaps this can be done by getting all members, their physical addresses and ports, and scanning the next N ports?

The UpgradeServers talk to each other when sending a message to one/all members.
@belaban belaban added the enhancement New feature or request label Nov 25, 2019
@belaban belaban mentioned this issue Nov 4, 2020
Open
@belaban belaban self-assigned this Nov 15, 2023
@belaban belaban transferred this issue from jgroups-extras/RollingUpgrades Dec 4, 2023
@belaban belaban added this to the 1.2 milestone Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@belaban belaban

Labels
enhancement New feature or request
Projects
None yet
Milestone
1.2
Development

No branches or pull requests
1 participant
@belaban