[
https://issues.apache.org/jira/browse/KAFKA-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457438#comment-15457438
]
ASF GitHub Bot commented on KAFKA-4115:
---------------------------------------
GitHub user shikhar opened a pull request:
https://github.com/apache/kafka/pull/1815
KAFKA-4115: grow default heap size for connect-distributed.sh to 1G
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shikhar/kafka connect-heap-opts
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1815.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1815
----
commit 1ceb80ed040ed0a5b988857273af5a2606f1df0b
Author: Shikhar Bhushan <shik...@confluent.io>
Date: 2016-09-02T04:01:27Z
KAFKA-4115: grow default heap size for connect-distributed.sh to 1G
----
> 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: Shikhar Bhushan
>
> 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.3.4#6332)
