Disable default disk threshold check in ElasticsearchContainer #7245
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
Elasticsearch stops writing to disk when the usage goes above 90%.
This problem can be hard to detect in CI environments.
Only after adding
.withLogConsumer(o -> log.info("elastic> {}", o.getUtf8String()))did I find out that Elastic had logged this kind of warning:high disk watermark [90%] exceeded on [WSN4y7xITamrUzTvic-eEg][94f6a74e1f83][/usr/share/elasticsearch/data] free: 8.1gb[9.7%], shards will be relocated away from this node; currently relocating away shards totalling [0] bytes; the node is expected to continue to exceed the high disk watermark when these relocations are complete
Modifications
Set
cluster.routing.allocation.disk.threshold_enabledtofalseto disable the disk threshold check.