You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/06/19 15:17:00 UTC
[jira] [Created] (KAFKA-5470) Replace -XX:+DisableExplicitGC with
-XX:+ExplicitGCInvokesConcurrent in kafka-run-class
Ismael Juma created KAFKA-5470:
----------------------------------
Summary: Replace -XX:+DisableExplicitGC with -XX:+ExplicitGCInvokesConcurrent in kafka-run-class
Key: KAFKA-5470
URL: https://issues.apache.org/jira/browse/KAFKA-5470
Project: Kafka
Issue Type: Improvement
Reporter: Ismael Juma
Priority: Critical
This is important because Bits.reserveMemory calls System.gc() hoping to free native memory in order to avoid throwing an OutOfMemoryException. This call is currently a no-op due to -XX:+DisableExplicitGC.
It's worth mentioning that -XX:MaxDirectMemorySize can be used to increase the amount of native memory available for allocation of direct byte buffers.
Hongyuan Li pointed out the issue with the usage of -XX:+DisableExplicitGC in: https://issues.apache.org/jira/browse/KAFKA-5444?focusedCommentId=16054129&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16054129
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)