[
https://issues.apache.org/jira/browse/KAFKA-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209613#comment-15209613
]
ASF GitHub Bot commented on KAFKA-3418:
---------------------------------------
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/1129
KAFKA-3418: add javadoc section describing consumer failure detection
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka KAFKA-3418
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1129.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 #1129
----
commit c632ccda0192bc3821a00dbd3108b5a96240acd7
Author: Jason Gustafson <ja...@confluent.io>
Date: 2016-03-24T02:13:03Z
KAFKA-3418: add javadoc section describing consumer failure detection
----
> Add section on detecting consumer failures in new consumer javadoc
> ------------------------------------------------------------------
>
> Key: KAFKA-3418
> URL: https://issues.apache.org/jira/browse/KAFKA-3418
> Project: Kafka
> Issue Type: Improvement
> Components: consumer
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Fix For: 0.10.0.0
>
>
> There still seems to be a lot of confusion about the design of the poll()
> loop in regard to consumer liveness. We do mention it in the javadoc, but
> it's a little hidden and we aren't very clear on what the user should do to
> limit the potential for the consumer to fall out of the group (such as
> tweaking max.poll.records). We should pull this into a separate section (e.g.
> Jay suggests "Detecting Consumer Failures") and give it a more complete
> treatment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
