You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/03/09 18:37:40 UTC

[jira] [Commented] (KAFKA-3318) Improve consumer rebalance error messaging

    [ https://issues.apache.org/jira/browse/KAFKA-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187478#comment-15187478 ] 

ASF GitHub Bot commented on KAFKA-3318:
---------------------------------------

GitHub user hachikuji opened a pull request:

    https://github.com/apache/kafka/pull/1036

    KAFKA-3318: clean up consumer logging and error messages

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/hachikuji/kafka KAFKA-3318

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1036.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 #1036
    
----
commit 274378395e48bca11350c1df3a38137810ba0732
Author: Jason Gustafson <ja...@confluent.io>
Date:   2016-03-09T01:42:11Z

    KAFKA-3318: clean up consumer logging and error messages

----


> Improve consumer rebalance error messaging
> ------------------------------------------
>
>                 Key: KAFKA-3318
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3318
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>
> A common problem with the new consumer is to have message processing take longer than the session timeout, causing an unexpected rebalance. Unfortunately, when this happens, the error messages are often cryptic (e.g. something about illegal generation) and contain no clear advice on what to do (e.g. increase session timeout). We should do a pass on error messages to ensure that users receive clear guidance on the problem and possible solutions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)