[
https://issues.apache.org/jira/browse/KAFKA-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16252713#comment-16252713
]
Randall Hauch commented on KAFKA-4115:
--------------------------------------
The {{kafka-run-class.sh}} current [sets the maximum heap
size](https://github.com/apache/kafka/blob/trunk/bin/kafka-run-class.sh#L214-L216).
By default the JDK will set the minimum size to the smaller of 1/4 of physical
memory or 1GB. However, we know that Java ergonomics are not correct in Docker
images prior to JDK 9 (there are some other cases), so IMO it is worthwhile to
set the minimum heap size to 256M (as [~wicknicks] did in his PR).
> Grow default heap settings for distributed Connect from 256M to 1G
> ------------------------------------------------------------------
>
> Key: KAFKA-4115
> URL: https://issues.apache.org/jira/browse/KAFKA-4115
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Reporter: Shikhar Bhushan
> Assignee: Arjun Satish
> Labels: newbie
>
> Currently, both {{connect-standalone.sh}} and {{connect-distributed.sh}}
> start the Connect JVM with the default heap settings from
> {{kafka-run-class.sh}} of {{-Xmx256M}}.
> At least for distributed connect, we should default to a much higher limit
> like 1G. While the 'correct' sizing is workload dependent, with a system
> where you can run arbitrary connector plugins which may perform buffering of
> data, we should provide for more headroom.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
