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.

Sign up for GitHub

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

Jump to bottom

[8.2] Adding a deprecation info API check for too many shards (#85967) #86518

Merged
merged 2 commits into from
May 6, 2022
Merged

[8.2] Adding a deprecation info API check for too many shards (#85967) #86518

merged 2 commits into from
May 6, 2022

Conversation

masseyke
Copy link
Member

@masseyke masseyke commented May 6, 2022

Backports the following commits to 8.2:

@masseyke
Adding a deprecation info API check for too many shards (elastic#85967)
2ea8a2b 
This commit makes sure that there is enough room in a cluster to add a small number of shards during an upgrade. The information is exposed in the deprecation info API as a cluster configuration check.
Closes elastic#85702
@masseyke masseyke added >non-issue auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport Team:Data labels May 6, 2022
@elasticsearchmachine elasticsearchmachine mentioned this pull request May 6, 2022
Merged
@elasticsearchmachine elasticsearchmachine merged commit a20b65f into elastic:8.2 May 6, 2022
@masseyke masseyke deleted the backport/8.2/pr-85967 branch May 6, 2022 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport >non-issue v8.2.1
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@masseyke @mark-vieira @elasticsearchmachine