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
Let's assume the case that we have a backend that has just restarted.
Once the backend starts up, it will presumably not be able to handle the load of requests that can come from the Carapace.
It would be interesting to be able to handle the case where the backend just went back UP. That is, as soon as the backend returns UP, for the first X seconds you should start with a low request load and gradually increase the request load.
This will probably mean that some requests will initially be pending, but still generally fewer requests should fail.
The text was updated successfully, but these errors were encountered:
NiccoMlt
changed the title
Insert a rate Limit between requests as soon as the backend is back UP recently
Insert a rate limit between requests as soon as the backend is back UP recently
Apr 9, 2024
Let's assume the case that we have a backend that has just restarted.
Once the backend starts up, it will presumably not be able to handle the load of requests that can come from the Carapace.
It would be interesting to be able to handle the case where the backend just went back UP. That is, as soon as the backend returns UP, for the first X seconds you should start with a low request load and gradually increase the request load.
This will probably mean that some requests will initially be pending, but still generally fewer requests should fail.
The text was updated successfully, but these errors were encountered: