[8.15] Fix memory limit check bytes to GB conversion (backport #13838) #13876
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/summary
This PR closed the issue #13837, by fixing the bytes to GB conversion in the fallback memory check.
Checklist
Update CHANGELOG.asciidocFor functional changes, consider:
How to test these changes
The easiest way to test this change is to create a custom cgroup with a memory limit that is larger than the total system memory, then start apm-server binary with the created cgroup. Observer APM Server logs for "cgroup memory limit exceed available memory, falling back to the total system memory".
Related issues
Changelog
==== Bug fixes
This is an automatic backport of pull request Fix memory limit check bytes to GB conversion #13838 done by Mergify.