Further reduce rabbitmq free disk space limit #2658
Merged
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
JaCoCo Test Coverage
|
chengjie8
changed the title
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.
After reviewing the failed integration test PRs, I discovered that RabbitMQ is still facing 'out of disk space' warnings in the GitHub Actions artifact logs. The Bitnami images are configured by default to use disk space equivalent to the host machine's total memory, which is 16G in this case. Despite having previously set the limit to 10G, assuming it would be adequate, it proved to be excessive. As a result, RabbitMQ in the integration tests continued to encounter disk space issues, blocking any incoming messages. This led to failures caused by prolonged waiting times and timeouts.