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] Improve error message when transforms are not enabled on any node #74837

Closed
sophiec20 opened this issue Aug 12, 2020 · 3 comments · Fixed by #98592
Closed

[ML] Improve error message when transforms are not enabled on any node #74837

sophiec20 opened this issue Aug 12, 2020 · 3 comments · Fixed by #98592
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Transforms ML transforms :ml usability v7.13.0

Comments

@sophiec20
Copy link
Contributor

Found in master "build_hash" : "5de0ed9432f4b41b697c9f3bc28953834cd3eae1", "build_date" : "2020-08-06T12:34:55.776311Z",

When node.roles: [ "transform" ] is not enabled on any node, then a transform cannot be run. The UI will let you step through the process of creating a transform, but the following error is displayed on start.

image

This node setting does not disable the API entirely, so GET _transform still works. But it does stop the transform from running on a node. If there are no nodes capable of starting the transform, then you will see this error.

Please can we improve the presentation of this error and make it more human read-able.

@sophiec20 sophiec20 added bug Fixes for quality problems that affect the customer experience usability Feature:Transforms ML transforms labels Aug 12, 2020
@peteharverson peteharverson self-assigned this Aug 17, 2020
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 12, 2021
@peteharverson peteharverson added :ml and removed needs-team Issues missing a team label labels Apr 21, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@walterra
Copy link
Contributor

In #93956 we added better UI degradation when transform roles are missing. The "Create transform" button is no longer available in such a case and a warning callout explains the reasons.

image

Leaving this issue still open for now as we investigate a possible regression introduced by this PR (elastic/elasticsearch#70125) where the transform list would no longer load because the _transform/_stats endpoint is no longer usable without a transform role.

@walterra
Copy link
Contributor

walterra commented Apr 27, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Transforms ML transforms :ml usability v7.13.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants