Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Tue, 5 Mar 2013 17:24:13 +0000 (UTC)
From: "Neha Narkhede (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12635374.1362503897542.384571.1362504253824@arcas>
In-Reply-To: <JIRA.12635374.1362503897542@arcas>
References: <JIRA.12635374.1362503897542@arcas>
Subject: [jira] [Updated] (KAFKA-787) Simple Consumer connecting to Broker
 that is not the Leader generates wrong error
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/KAFKA-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neha Narkhede updated KAFKA-787:
--------------------------------

    Labels: kafka-0.8 p2  (was: )
    
> 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
>
> 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