[
https://issues.apache.org/jira/browse/KAFKA-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16252696#comment-16252696
]
ASF GitHub Bot commented on KAFKA-4115:
---------------------------------------
GitHub user wicknicks opened a pull request:
https://github.com/apache/kafka/pull/4213
KAFKA-4115: Increasing the heap settings for connect-distributed script
Signed-off-by: Arjun Satish <ar...@confluent.io>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wicknicks/kafka KAFKA-4115
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/4213.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 #4213
----
commit 51e6404ec090de6d6f8919e3abe78a955ac60d7a
Author: Arjun Satish <ar...@confluent.io>
Date: 2017-11-14T23:33:37Z
Increasing the heap settings for connect-distributed script
Signed-off-by: Arjun Satish <ar...@confluent.io>
----
> 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)
