You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Viktor Somogyi-Vass (Jira)" <ji...@apache.org> on 2019/10/10 13:43:00 UTC

[jira] [Created] (KAFKA-9016) Warn when log dir stopped serving replicas

Viktor Somogyi-Vass created KAFKA-9016:
------------------------------------------

             Summary: Warn when log dir stopped serving replicas
                 Key: KAFKA-9016
                 URL: https://issues.apache.org/jira/browse/KAFKA-9016
             Project: Kafka
          Issue Type: Improvement
          Components: log, log cleaner
            Reporter: Viktor Somogyi-Vass


Kafka should warn if the log directory stops serving replicas as usually it is due to an error and it's much visible if it's on warn level.

{noformat}
2019-09-19 12:39:54,194 ERROR kafka.server.LogDirFailureChannel: Error while writing to checkpoint file /kafka/data/diskX/replication-offset-checkpoint
java.io.SyncFailedException: sync failed
..
2019-09-19 12:39:54,197 INFO kafka.server.ReplicaManager: [ReplicaManager broker=638] Stopping serving replicas in dir /kafka/data/diskX
..
2019-09-19 12:39:54,205 INFO kafka.server.ReplicaFetcherManager: [ReplicaFetcherManager on broker 638] Removed fetcher for partitions Set(test1-0, test2-2, test-0, test2-2, test4-14, test4-0, test2-6)
2019-09-19 12:39:54,206 INFO kafka.server.ReplicaAlterLogDirsManager: [ReplicaAlterLogDirsManager on broker 638] Removed fetcher for partitions Set(test1-0, test2-2, test-0, test3-2, test4-14, test4-0, test2-6)
2019-09-19 12:39:54,222 INFO kafka.server.ReplicaManager: [ReplicaManager broker=638] Broker 638 stopped fetcher for partitions test1-0,test2-2,test-0,test3-2,test4-14,test4-0,test2-6 and stopped moving logs for partitions  because they are in the failed log directory /kafka/data/diskX.

{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)