[
https://issues.apache.org/jira/browse/KAFKA-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211231#comment-15211231
]
ASF GitHub Bot commented on KAFKA-3463:
---------------------------------------
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/1140
KAFKA-3463: change default receive buffer size for consumer to 64K
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka KAFKA-3463
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1140.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 #1140
----
commit 3bd92aea373dad3c8cbdc0ee3f99e7d035f99b63
Author: Jason Gustafson <ja...@confluent.io>
Date: 2016-03-25T00:57:31Z
KAFKA-3463: change default receive buffer size for consumer to 64K
----
> Change default consumer receive buffer size to 64K
> --------------------------------------------------
>
> Key: KAFKA-3463
> URL: https://issues.apache.org/jira/browse/KAFKA-3463
> Project: Kafka
> Issue Type: Improvement
> Components: consumer
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Fix For: 0.10.0.0
>
>
> In KAFKA-3135, users have reported a strange pause when consuming data using
> the new consumer. This can be easily reproduced with the console consumer,
> but the root cause has so far proven elusive. Interestingly, the pause can
> also be reproduced with the old consumer if you change the socket buffer size
> to 32K to match the new consumer's default. Similarly, by increasing the new
> consumer's connection receive buffer size to 64K to match the old consumer's
> default, the problem seems to be mitigated (I am unable to reproduce it
> locally with this setting, though others have reported that its impact is
> merely reduced). Since there doesn't appear to be a good reason to have
> lowered the default for the new consumer, we may as well revert to the old
> consumer's default of 64K and accept the mitigation until an actual fix is
> found.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
