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

k8s feature: Leader election #1040

Open
rvowles opened this issue Jul 28, 2023 · 0 comments
Open

k8s feature: Leader election #1040

rvowles opened this issue Jul 28, 2023 · 0 comments

Comments

@rvowles
Copy link
Contributor

rvowles commented Jul 28, 2023

For people who run FeatureHub in k8s, we should have some way of indicating this so we can enable k8s specific capability.

Particularly there is leader election for the Management Repository. If we enable Leader Election, then ideally when features are updated, as part of the same transaction that will also insert a new record into a new "publish" table. The leader should monitor this table and publish data within it, making MR resilient to the situation where the messaging layer goes offline.

This would remove NATS from being a Health Check source and more of an indicator for MR to stop and restart publishing.

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