[7312] Fix Elasticsearch container OOM failures in CI #7313
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.
Added container memory limit of 700MB to prevent out-of-memory issues in CI environments. The JVM heap was already limited to 512MB via ES_JAVA_OPTS, but the container itself had no memory constraint, causing Elasticsearch to request more memory than available and be killed by the OOM killer.
🤖 Generated with Claude Code