Repository navigation
[BUG] The rocketmq 4.9.6 still use 'free' to get system memory #114
Description
The issue tracker is ONLY used for bug report(feature request need to follow RIP process). Keep in mind, please check whether there is an existing same report before your raise a new one.
Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration and other improvements.
Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following:
BUG REPORT
- Please describe the issue you observed:
-
What did you do (The steps to reproduce)?
get Rocketmq 4.9.6 from docker hub: https://hub.docker.com/r/apache/rocketmq/tags?name=4.9.6 -
What did you expect to see?
Incalculate_heap_sizesfunction, get system memory from cgroup or env -
What did you see instead?
get system memory from 'free' cmd
Activity
lfq1234 commentedon Jun 7, 2025
The early versions of RocketMQ used the
freecommand to get system memory because it was simple and direct. Although better methods exist, the development team has kept the current approach to ensure backward compatibility and avoid introducing new issues through code changes, which require rigorous testing and validation.