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] Allow a force delete for analytics jobs #48124

Closed
sophiec20 opened this issue Oct 16, 2019 · 1 comment · Fixed by #50553
Closed

[ML] Allow a force delete for analytics jobs #48124

sophiec20 opened this issue Oct 16, 2019 · 1 comment · Fixed by #50553
Assignees
Labels
>enhancement :ml Machine learning

Comments

@sophiec20
Copy link
Contributor

For jobs which may have failed, there is currently a two step process to delete this job. First it must be force closed, then it can be deleted.

We should allow a force delete action so that:

  • it allows a single step delete for failed jobs
  • it matches anomaly and transform options
  • we can stop in-progress analytics jobs quicker as we do not need to wait for any state to be saved as it is about to be deleted (note, this was true for anomaly detection)
@sophiec20 sophiec20 added >enhancement :ml Machine learning labels Oct 16, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml)

@dimitris-athanasiou dimitris-athanasiou self-assigned this Jan 2, 2020
dimitris-athanasiou added a commit to dimitris-athanasiou/elasticsearch that referenced this issue Jan 2, 2020
Adds a `force` parameter to the delete data frame analytics
request. When `force` is `true`, the action force-stops the
jobs and then proceeds to the deletion. This can be used in
order to delete a non-stopped job with a single request.

Closes elastic#48124
dimitris-athanasiou added a commit that referenced this issue Jan 3, 2020
Adds a `force` parameter to the delete data frame analytics
request. When `force` is `true`, the action force-stops the
jobs and then proceeds to the deletion. This can be used in
order to delete a non-stopped job with a single request.

Closes #48124
dimitris-athanasiou added a commit to dimitris-athanasiou/elasticsearch that referenced this issue Jan 3, 2020
…c#50553)

Adds a `force` parameter to the delete data frame analytics
request. When `force` is `true`, the action force-stops the
jobs and then proceeds to the deletion. This can be used in
order to delete a non-stopped job with a single request.

Closes elastic#48124

Backport of elastic#50553
dimitris-athanasiou added a commit that referenced this issue Jan 3, 2020
#50589)

Adds a `force` parameter to the delete data frame analytics
request. When `force` is `true`, the action force-stops the
jobs and then proceeds to the deletion. This can be used in
order to delete a non-stopped job with a single request.

Closes #48124

Backport of #50553
SivagurunathanV pushed a commit to SivagurunathanV/elasticsearch that referenced this issue Jan 23, 2020
Adds a `force` parameter to the delete data frame analytics
request. When `force` is `true`, the action force-stops the
jobs and then proceeds to the deletion. This can be used in
order to delete a non-stopped job with a single request.

Closes elastic#48124
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement :ml Machine learning
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants