MrLYG opened a new issue, #201: URL: https://github.com/apache/rocketmq-operator/issues/201
https://github.com/apache/rocketmq-operator/blob/a8665716c8028741ec106814798e39fe07e6dcaa/images/broker/alpine/runbroker-customize.sh#L57C34-L57C73 I've noticed that the system command `free` is used to obtain resource information in our Kubernetes setup. This command retrieves the entire system's resource status, rather than the resource limits of individual containers. This behavior leads to a significant issue: if the memory allocated to a pod in Kubernetes is substantially smaller than the host's total memory, the pod can encounter Out-Of-Memory (OOM) errors. I believe I can contribute to addressing this issue. My approach would involve modifying the relevant part of our system to ensure that the resource queries are container-aware, possibly by accessing cgroup data directly for more accurate readings of container-specific limits. I am ready to start working on this and plan to submit a pull request (PR) with the proposed changes. Please let me know if there are any specific guidelines or processes I should follow for this contribution. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
