[
https://issues.apache.org/jira/browse/KAFKA-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332767#comment-15332767
]
Jason Rosenberg commented on KAFKA-3536:
----------------------------------------
which version are you seeing this in (I'm seeing it just now in 0.8.2.2), after
a server restart....
> ReplicaFetcherThread should not log errors when leadership changes
> ------------------------------------------------------------------
>
> Key: KAFKA-3536
> URL: https://issues.apache.org/jira/browse/KAFKA-3536
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Reporter: Stig Rohde Døssing
> Priority: Minor
>
> When there is a leadership change, ReplicaFetcherThread will spam the log
> with errors similar to the log snippet below.
> {noformat}
> [ReplicaFetcherThread-0-2], Error for partition [ticketupdate,7] to broker
> 2:class kafka.common.NotLeaderForPartitionException
> (kafka.server.ReplicaFetcherThread)
> {noformat}
> ReplicaFetcherThread/AbstractFetcherThread should log those exceptions at a
> lower log level, since they don't actually indicate an error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
