You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 with200 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
The text was updated successfully, but these errors were encountered: