-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[Transform] stop transform regardless of transform nodes #69419
[Transform] stop transform regardless of transform nodes #69419
Conversation
….g. if the cluster lacks a transform node)
e6628b8
to
2e4d72c
Compare
Pinging @elastic/ml-core (Team:ML) |
.../plugin/transform/src/main/java/org/elasticsearch/xpack/transform/action/TransformNodes.java
Outdated
Show resolved
Hide resolved
...ansform/src/main/java/org/elasticsearch/xpack/transform/action/TransformNodeAssignments.java
Outdated
Show resolved
Hide resolved
.../plugin/transform/src/main/java/org/elasticsearch/xpack/transform/action/TransformNodes.java
Outdated
Show resolved
Hide resolved
Co-authored-by: David Kyle <[email protected]>
run elasticsearch-ci/bwc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
...ansform/src/main/java/org/elasticsearch/xpack/transform/action/TransformNodeAssignments.java
Outdated
Show resolved
Hide resolved
}, e -> { | ||
if (e instanceof ResourceNotFoundException) { | ||
Tuple<Set<String>, Set<String>> runningTasksAndNodes = findTasksWithoutConfig(state, request.getId()); | ||
if (runningTasksAndNodes.v1().isEmpty()) { | ||
listener.onFailure(e); | ||
// found transforms without a config | ||
} else if (request.isForce()) { | ||
// TODO: handle tasks waiting for assignment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, what is there left to do? Aren't waiting tasks handled by cancelTransformTasksWithNoAssignment
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the special case were the transform "lost" the configuration, meaning it could not be found in the transform index. This happens if you e.g. manually delete the document or the whole index.
I still think we should handle it, but I like to postpone it to the follow up, I added the todo there.
...orm/src/main/java/org/elasticsearch/xpack/transform/action/TransportStopTransformAction.java
Outdated
Show resolved
Hide resolved
...orm/src/main/java/org/elasticsearch/xpack/transform/action/TransportStopTransformAction.java
Outdated
Show resolved
Hide resolved
...orm/src/main/java/org/elasticsearch/xpack/transform/action/TransportStopTransformAction.java
Outdated
Show resolved
Hide resolved
Co-authored-by: Przemysław Witek <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
allow stop transform to stop a transform task if its waiting for assignment(e.g. if the cluster lacks a transform node) fixes elastic#69260
allow stop transform to stop a transform task if its waiting for assignment(e.g. if the cluster lacks a transform node) fixes elastic#69260
allow stop transform to stop a transform task if its waiting for assignment(e.g. if
the cluster lacks a transform node)
fixes #69260