Skip to content

[DOCS] Documents that models with one allocation might have downtime #2567

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

Merged
merged 3 commits into from
Oct 18, 2023

Conversation

szabosteve
Copy link
Contributor

@szabosteve szabosteve commented Oct 17, 2023

Overview

This PR adds an IMPORTANT block to the trained model deployment section that explains that users will experience downtime in the service of their trained model if the model has only one allocation deployed.

Preview

Deploy the model to your cluster

@szabosteve szabosteve added :ml nlp v8.9.0 backport-8.9 Automated backport with mergify v8.10 backport-8.10 Automated backport with mergify v8.11 backport-8.11 Automated backport with mergify v8.12 labels Oct 17, 2023
@github-actions
Copy link

Documentation preview:

@szabosteve szabosteve marked this pull request as ready for review October 17, 2023 14:34
@szabosteve szabosteve changed the title [DOCS] Documents that models with one allocations might have downtime [DOCS] Documents that models with one allocation might have downtime Oct 17, 2023
@wwang500
Copy link

Hmm, I think this case is for serverless projects only, is it? @droberts195 ?

@droberts195
Copy link
Contributor

serverless projects only

No, it affects all types of installation - on-premise, classic Cloud and serverless. If a model is only running on one node then it won't be able to service requests when that node gets restarted for any reason.

Copy link

@wwang500 wwang500 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

@droberts195 droberts195 left a comment

Choose a reason for hiding this comment

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

LGTM

@szabosteve szabosteve merged commit c252428 into elastic:main Oct 18, 2023
@szabosteve szabosteve deleted the nlp-model-allocation branch October 18, 2023 09:26
mergify bot pushed a commit that referenced this pull request Oct 18, 2023
…2567)

* [DOCS] Documents that models with one allocations might have downtime.

* [DOCS] Fine-tunes wording.

(cherry picked from commit c252428)
mergify bot pushed a commit that referenced this pull request Oct 18, 2023
…2567)

* [DOCS] Documents that models with one allocations might have downtime.

* [DOCS] Fine-tunes wording.

(cherry picked from commit c252428)
mergify bot pushed a commit that referenced this pull request Oct 18, 2023
…2567)

* [DOCS] Documents that models with one allocations might have downtime.

* [DOCS] Fine-tunes wording.

(cherry picked from commit c252428)
szabosteve added a commit that referenced this pull request Oct 18, 2023
szabosteve added a commit that referenced this pull request Oct 18, 2023
szabosteve added a commit that referenced this pull request Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.9 Automated backport with mergify backport-8.10 Automated backport with mergify backport-8.11 Automated backport with mergify :ml nlp v8.9.0 v8.10 v8.11 v8.12
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants