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] readiness endpoint #1029

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

[FEATURE] readiness endpoint #1029

rotarur opened this issue Oct 19, 2024 · 1 comment

Comments

@rotarur
Copy link

rotarur commented Oct 19, 2024

When restarting the indexer it takes some time to load all the resources and to check all SG's. during this loading period the loadbalancer is sending traffic to the pod and those queries fail increasing the error rate.

I'd like to propose to create a /ready readiness endpoint which starts to respond with 200 http code only after everything was loaded and checked. This will allow the loadbalancer to know when to start sending traffic to the backend.

We could configure a delay for the traffic to be sent to the backends but that's a static configuration and sometimes it takes less / more time than usual so better is to have an endpoint that we could configure the loadbalancer to query to know when to send traffic

@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 it to the new indexer-rs graphprotocol/indexer-rs#504

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