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

Inject address for peers at storage controller start-up #101

Merged
merged 3 commits into from
Aug 20, 2024

Conversation

VladLazar
Copy link
Contributor

The storage controller needs to know the address at which it is reachable by it's peers within the deployment. It will use this to mark itself as the leader in the database.

The CLI arg was added in neondatabase/neon#8588 and that's already been deployed everywhere.

Note that we are not enabling graceful leadership tranfers with this change. The only change in storcon behaviour is that each instance will write its address into the database at start-up. If that fails, the process exits.

The storage controller needs to know the address at which it is
reachable by it's peers within the deployment. It will use this
to mark itself as the leader in the database.

The CLI arg was added in neondatabase/neon#8588
and that's already been deployed everywhere.

Note that we are not enabling graceful leadership tranfers with this
change. The only change in storcon behaviour is that each instance
will write its address into the database at start-up. If that fails,
the process exits.
@VladLazar VladLazar force-pushed the vlad/external-ip-for-storcon-pods branch from 6a30793 to b3ea006 Compare August 20, 2024 12:35
@VladLazar VladLazar marked this pull request as ready for review August 20, 2024 12:43
@VladLazar VladLazar merged commit 9c25701 into main Aug 20, 2024
3 checks passed
@VladLazar VladLazar deleted the vlad/external-ip-for-storcon-pods branch August 20, 2024 13:12
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

Successfully merging this pull request may close these issues.

2 participants