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

Explore using more Elasticsearch response codes to pause or stop model indexer autoscaling #9511

Open
marclop opened this issue Nov 4, 2022 · 0 comments

Comments

@marclop
Copy link
Contributor

marclop commented Nov 4, 2022

As a follow up from #9463, it was suggested we may want to explore more HTTP response codes from Elasticsearch as a way to limit or stop autoscaling actions from taking place (or downscaling actions to be triggered).

Some other status codes we may consider is looking for 499 (client timeouts?), 502 and 503. All these may signal that Elasticsearch isn't fully responsive and that autoscaling should be paused if a certain rate is exceeded.

We're not collecting any of these metrics already in the model indexer stats and they would incur a slight storage cost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant