Skip to content

Conversation

@guvenc
Copy link
Collaborator

@guvenc guvenc commented May 6, 2024

Change the client behaviour in such a way that in case a second metalbond server distributing the exact same routes as the "main" server is added to the server list then the client is aware of the second server when adding removing the routes from its routing table hence withdraws already received routes only if both servers withdraw the routes in question.

Single server operation is same as before. (Backward compatible)

@github-actions github-actions bot added size/L enhancement New feature or request labels May 6, 2024
@guvenc guvenc marked this pull request as draft May 6, 2024 11:22
Change the client behaviour in such a way that in case
a second metalbond server distributing the exact some
routes as the "main" server is added to the server list
then the client is aware of the second server when adding
removing the routes from its routing table hence withdraws
already received routes only if both servers withdraw
the routes in question.

Single server operation is same as before. (Backward compatible)

Signed-off-by: Guvenc Gulce <guevenc.guelce@sap.com>
@guvenc guvenc force-pushed the feature/ha_support branch from d47c123 to d5b7730 Compare May 6, 2024 14:28
@guvenc guvenc linked an issue May 8, 2024 that may be closed by this pull request
@hardikdr hardikdr added the area/networking Networking-related tasks and improvements. label May 5, 2025
@hardikdr hardikdr added this to Roadmap Jun 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/networking Networking-related tasks and improvements. enhancement New feature or request size/L

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

Introduce High Availability support for metalbond

3 participants