You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2019/10/11 22:13:00 UTC

[jira] [Updated] (KAFKA-7981) Add Replica Fetcher and Log Cleaner Count Metrics

     [ https://issues.apache.org/jira/browse/KAFKA-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson updated KAFKA-7981:
-----------------------------------
    Affects Version/s:     (was: 2.3.0)

> Add Replica Fetcher and Log Cleaner Count Metrics
> -------------------------------------------------
>
>                 Key: KAFKA-7981
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7981
>             Project: Kafka
>          Issue Type: Improvement
>          Components: metrics
>            Reporter: Viktor Somogyi-Vass
>            Assignee: Viktor Somogyi-Vass
>            Priority: Major
>              Labels: kip
>             Fix For: 2.5.0
>
>
> In some occasions we detected errors where replica fetcher threads or log cleaners died because of an unrecoverable error and caused more serious issues in the brokers (from lagging to offline replicas, filling up disks, etc.). It would often help if the monitoring systems attached to Kafka could detect these problems early on as it would allow a prompt response from the user and the greater possibility of capturing the root cause.



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