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

[ML] Better handling of job request timeouts #20985

Conversation

jgowdyelastic
Copy link
Member

When performing actions on multiple jobs, the jobs are looped over and run synchronously to avoid strain on the server.
There is a 30s timeout when calling java endpoints and if any of these hit the timeout, the loop will progress to the next job causing a situation where multiple requests are running at the same time.
This change causes the loop to break and return timeout failures for all of the jobs which haven't yet been dealt with.

Also moves groups getAllGroups into it's own file and slightly adjusts the width of a column to accommodate hard_limit and soft_limit memory statuses.

Unit tests to follow in a subsequent PR.

@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui

Copy link
Contributor

@walterra walterra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@peteharverson peteharverson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@jgowdyelastic
Copy link
Member Author

Related to #20150

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

Successfully merging this pull request may close these issues.

4 participants