[ https://issues.apache.org/jira/browse/KAFKA-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658686#comment-14658686 ]
ASF GitHub Bot commented on KAFKA-2400: --------------------------------------- GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/116 KAFKA-2400; expose heartbeat interval in KafkaConsumer configuration You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-2400 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/116.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 #116 ---- commit 3c1b1dd0dc44cd454d02aa7c476825ceeee2ba46 Author: Jason Gustafson <ja...@confluent.io> Date: 2015-08-05T18:52:35Z KAFKA-2400; expose heartbeat interval in KafkaConsumer configuration ---- > Expose heartbeat frequency in new consumer configuration > -------------------------------------------------------- > > Key: KAFKA-2400 > URL: https://issues.apache.org/jira/browse/KAFKA-2400 > Project: Kafka > Issue Type: Sub-task > Reporter: Jason Gustafson > Assignee: Jason Gustafson > Priority: Minor > > The consumer coordinator communicates the need to rebalance through responses > to heartbeat requests sent from each member of the consumer group. The > heartbeat frequency therefore controls how long normal rebalances will take. > Currently, the frequency is hard-coded to 3 heartbeats per the configured > session timeout, but it would be nice to expose this setting so that the user > can control the impact from rebalancing. > Since the consumer is currently single-threaded and heartbeats are sent in > poll(), we cannot guarantee that the heartbeats will actually be sent at the > configured frequency. In practice, the user may have to adjust their fetch > size to ensure that poll() is called often enough to get the desired > heartbeat frequency. For most users, the consumption rate is probably fast > enough for this not to matter, but we should make the documentation clear on > this point. In any case, we expect that most users will accept the default > value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)