Preflight check for usable space and cache size #21031
Open
+181
−1
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 PR is adding a datanode preflight check comparing the usable disk space and the setting of node search cache. Recently, there were several complains that datanodes are running out of space and it was not clear why. This preflight check will either terminate the startup if the cache consumes all of the usable space or warn if the cache is over 80% of the space.
With this, users should get better overview and an action recommendation in case the datanode is running on very limited storage and the cache could cause problems with watermark levels inside opensearch.
How Has This Been Tested?
Added unit tests, existing set of integration tests for valid startups.
Types of changes
Checklist: