You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2013/03/08 03:02:12 UTC

[jira] [Commented] (KAFKA-787) Simple Consumer connecting to Broker that is not the Leader generates wrong error

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

Jun Rao commented on KAFKA-787:
-------------------------------

+1
                
> Simple Consumer connecting to Broker that is not the Leader generates wrong error
> ---------------------------------------------------------------------------------
>
>                 Key: KAFKA-787
>                 URL: https://issues.apache.org/jira/browse/KAFKA-787
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8
>            Reporter: Chris Curtin
>            Assignee: Neha Narkhede
>              Labels: kafka-0.8, p2
>         Attachments: kafka-787.patch
>
>
> 0.8.0 HEAD from 3/4/2013
> Using a SimpleConsumer, connect to a Broker that is NOT the leader for the topic/partition you want to fetch, but IS a replica.
> On fetch the error returned is '5' 'ErrorMapping.LeaderNotAvailableCode'
> Per email thread with Neha:
> "Ideally, you should get back  ErrorMapping.NotLeaderForPartitionCode"
> Key part of the test is the Broker must be a replica. If the topic/partition is not on the Broker you get a different (correct) error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira