smengcl opened a new pull request, #10354: URL: https://github.com/apache/ozone/pull/10354
## What changes were proposed in this pull request? Adds two opt-in env vars in `ozone_java_setup` to cap Netty's pooled direct memory: - `OZONE_NETTY_MAX_DIRECT_MEMORY` sets `-Dio.netty.maxDirectMemory=<bytes>` (unshaded `io.netty`, used by S3G/gRPC). - `OZONE_RATIS_NETTY_MAX_DIRECT_MEMORY` sets `-Dorg.apache.ratis.thirdparty.io.netty.maxDirectMemory=<bytes>` (Ratis-shaded copy, used by DN write/replication). Two variables are needed because the unshaded and Ratis-shaded Netty classes have independent allocators, each defaulting to `≈ -Xmx` — so the implicit per-process ceiling is roughly `2 × -Xmx` of direct memory. Both env vars are unset by default. No behavior change unless operators set them. Companion docs PR in `apache/ozone-site` adds `docs/06-troubleshooting/17-netty-direct-memory.md`. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-11234 ## How was this patch tested? - Manually confirmed each `-D` lands in the correct `OPTS` var. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
