[
https://issues.apache.org/jira/browse/KAFKA-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642346#comment-13642346
]
BalajiSeshadri edited comment on KAFKA-816 at 4/25/13 11:02 PM:
----------------------------------------------------------------
I see fix merged in the show log but it is not working.
SHA-1: 51421fcc0111031bb77f779a6f6c00520d526a34
* KAFKA-816 Reduce noise in Kafka server logs due to
NotLeaderForPartitionException; reviewed by Jun Rao
was (Author: balaji.sesha...@dish.com):
I see fix merged in the show log.
SHA-1: 51421fcc0111031bb77f779a6f6c00520d526a34
* KAFKA-816 Reduce noise in Kafka server logs due to
NotLeaderForPartitionException; reviewed by Jun Rao
> 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.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
