You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Stig Rohde Døssing (JIRA)" <ji...@apache.org> on 2016/04/11 15:12:25 UTC
[jira] [Created] (KAFKA-3536) ReplicaFetcherThread should not log
errors when leadership changes
Stig Rohde Døssing created KAFKA-3536:
-----------------------------------------
Summary: 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)