You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2013/03/19 23:11:15 UTC

[jira] [Created] (KAFKA-816) Reduce noise in Kafka server logs due to NotLeaderForPartitionException

Neha Narkhede created KAFKA-816:
-----------------------------------

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


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