-
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
[@kbn/es] Disable ES disk usage threshold #123674
Merged
tylersmalley
merged 2 commits into
elastic:main
from
tylersmalley:kbn-es-disable-watermark
Mar 1, 2022
Merged
[@kbn/es] Disable ES disk usage threshold #123674
tylersmalley
merged 2 commits into
elastic:main
from
tylersmalley:kbn-es-disable-watermark
Mar 1, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tylersmalley
added
Team:Operations
Team label for Operations Team
v8.1.0
release_note:skip
Skip the PR/issue when compiling release notes
labels
Jan 25, 2022
tylersmalley
force-pushed
the
kbn-es-disable-watermark
branch
from
March 1, 2022 06:48
22e2994
to
f0639fe
Compare
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
tylersmalley
added
v8.0.0
v8.2.0
v7.17.2
auto-backport
Deprecated - use backport:version if exact versions are needed
labels
Mar 1, 2022
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
tylersmalley
changed the title
[@kbn/es] Disable ES threshold
[@kbn/es] Disable ES disk usage threshold
Mar 1, 2022
Pinging @elastic/kibana-operations (Team:Operations) |
brianseeders
approved these changes
Mar 1, 2022
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Mar 1, 2022
(cherry picked from commit 49ad584)
💔 Some backports could not be created
How to fixRe-run the backport manually:
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
tylersmalley
pushed a commit
to tylersmalley/kibana
that referenced
this pull request
Mar 1, 2022
(cherry picked from commit 49ad584) # Conflicts: # packages/kbn-es/src/cluster.js # packages/kbn-es/src/integration_tests/cluster.test.js
tylersmalley
pushed a commit
to tylersmalley/kibana
that referenced
this pull request
Mar 1, 2022
(cherry picked from commit 49ad584)
tylersmalley
pushed a commit
that referenced
this pull request
Mar 1, 2022
kibanamachine
added a commit
that referenced
this pull request
Mar 1, 2022
tylersmalley
pushed a commit
that referenced
this pull request
Mar 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-backport
Deprecated - use backport:version if exact versions are needed
release_note:skip
Skip the PR/issue when compiling release notes
Team:Operations
Team label for Operations Team
v7.17.2
v8.0.0
v8.1.0
v8.2.0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This often creates issues for developers who live on the edge of their disk usage. This is mostly a check for production to ensure it doesn't result in a disruption of the service or data loss, so let's disable it for development.