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

[FEATURE] healthy endpoint #1030

Open
rotarur opened this issue Oct 19, 2024 · 1 comment
Open

[FEATURE] healthy endpoint #1030

rotarur opened this issue Oct 19, 2024 · 1 comment

Comments

@rotarur
Copy link

rotarur commented Oct 19, 2024

When some pod has an issue to connect to the database or any other dependent service, it's still healthy for the loadbalancer which send traffic to it increasing the errors for the customers.

In order to reduce or completely remove the errors during these connection issues I'd like to propose to add a /healtz (yes it's written healthz instead of health to avoid overlapping with any other similar endpoint for the application and it's a common usage to name this one like that for the kubernetes) which will tell the loadbalancer that the pod is not healthy and to stop sending traffic to it. This endpoint will also help kubelet in kubernetes (or any other automated process) to restart that unhealthy pod before it's becoming critical to the whole system.

@github-project-automation github-project-automation bot moved this to 🗃️ Inbox in Indexer Oct 19, 2024
@rotarur
Copy link
Author

rotarur commented Nov 21, 2024

this can be closed now, I copied this to the new indexer-rs repo graphprotocol/indexer-rs#503

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🗃️ Inbox
Development

No branches or pull requests

1 participant