Skip to content

[8.4] Autoscaling after clone fix (#89768) #89786

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

Conversation

henningandersen
Copy link
Contributor

Backports the following commits to 8.4:

* Autoscaling after clone fix

Autoscaling could start failing after a clone, if the source of
the clone is deleted.

* Update docs/changelog/89768.yaml

* Update docs/changelog/89768.yaml
@henningandersen henningandersen added :Distributed Coordination/Autoscaling >bug auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. labels Sep 2, 2022
@elasticsearchmachine elasticsearchmachine merged commit 935d139 into elastic:8.4 Sep 2, 2022
@henningandersen henningandersen deleted the backport/8.4/pr-89768 branch September 2, 2022 04:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport >bug :Distributed Coordination/Autoscaling Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. v8.4.2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants