Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Tue, 19 Mar 2013 23:19:15 +0000 (UTC)
From: "Neha Narkhede (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12637838.1363730973156.15754.1363735155735@arcas>
In-Reply-To: <JIRA.12637838.1363730973156@arcas>
References: <JIRA.12637838.1363730973156@arcas>
Subject: [jira] [Updated] (KAFKA-816) Reduce noise in Kafka server logs due
 to NotLeaderForPartitionException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Neha Narkhede updated KAFKA-816:
--------------------------------

    Status: Patch Available  (was: In Progress)
    
> Reduce noise in Kafka server logs due to NotLeaderForPartitionException
> -----------------------------------------------------------------------
>
>                 Key: KAFKA-816
>                 URL: https://issues.apache.org/jira/browse/KAFKA-816
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8
>            Reporter: Neha Narkhede
>            Assignee: Neha Narkhede
>            Priority: Blocker
>              Labels: kafka-0.8, p2
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> NotLeaderForPartitionException is logged at the ERROR level with a full stack trace. But really this is just an informational message on the server when a client with stale metadata sends requests to the wrong leader for a partition. This floods the logs either if there are many clients or few clients sending many topics (migration tool or mirror maker). This should probably be logged at WARN and without the stack trace

--
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