-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Support force
stop deployment
#118563
[ML] Support force
stop deployment
#118563
Conversation
Pinging @elastic/ml-ui (:ml) |
title={ | ||
<FormattedMessage | ||
id="xpack.ml.trainedModels.modelsList.forceStopDialog.title" | ||
defaultMessage="Force stop model {modelId}?" |
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.
I'd suggest removing the term Force
from this dialog, as it seems like an API level detail that doesn't need to be shown in the UI.
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.
@peteharverson FYI the DFA page contains the "Force stop" action
Line 34 in 8126488
defaultMessage: 'Force stop', |
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.
Changed in 9ed4433
> | ||
<FormattedMessage | ||
id="xpack.ml.trainedModels.modelsList.forceStopDialog.pipelinesWarning" | ||
defaultMessage="Selected model has associated pipelines: " |
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.
Maybe reword to something like The selected model is being used by the following pipelines:
@lcawl any thoughts on the text in this dialog?
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.
IMO the impact is unclear. Will the ingest pipelines fail until you start a new deployment or will the inference processor just be skipped? Perhaps something like this:
You can't use these ingest pipelines until you restart the model:
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.
Changed in 9ed4433
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.
Any index request hitting a pipeline that refers to a model that doesn't have a started deployment will fail. The bulk response will contain an item for each one of them explaining the model wasn't deployed.
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.
Thanks! I've added similar information in the docs and API spec via elastic/elasticsearch#81026 and elastic/elasticsearch-specification#1061
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: cc @darnautov |
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.
Text LGTM
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
* support force stop * fix i18n, revert tests * update text * remove "Force" from the confirmation modals
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
* [ML] Support `force` stop deployment (#118563) * support force stop * fix i18n, revert tests * update text * remove "Force" from the confirmation modals * update i18n import Co-authored-by: Dima Arnautov <[email protected]>
* support force stop * fix i18n, revert tests * update text * remove "Force" from the confirmation modals
Summary
Adds support for
force
stop.If the model has associated pipelines, asks for the user confirmation to perform force stop deployment.
Checklist