[
https://issues.apache.org/jira/browse/KAFKA-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669434#comment-13669434
]
Neha Narkhede commented on KAFKA-816:
-------------------------------------
Balaji,
That fix was to reduce the noise in the kafka server logs. The error you see is
on the consumer when the leader for some partitions is failing over to another
replica. Can you please move the issue to a separate JIRA?
> 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
> Attachments: KAFKA-816.jpg, kafka-816.patch, kafka-816-v2.patch
>
> 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
