kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5135) Controller Health Metrics (KIP-143)
Date Thu, 27 Apr 2017 14:09:04 GMT

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

Ismael Juma updated KAFKA-5135:
-------------------------------
    Description: 
Ensuring that the Kafka Controller is healthy is an important part of monitoring the health
of a Kafka Cluster. However, the metrics currently exposed are not sufficient for reliably
detecting issues like slow progress or deadlocks. We propose a few new metrics that will solve
this issue. Even though KAFKA-5028 will potentially fix existing deadlocks, there will still
be known (and potentially unknown) issues that can cause slow or no progress so these metrics
will still be useful.

KIP:

https://cwiki.apache.org/confluence/display/KAFKA/KIP-143%3A+Controller+Health+Metrics

  was:
Ensuring that the Kafka Controller is healthy is an important part of monitoring the health
of a Kafka Cluster. However, the metrics currently exposed are not sufficient for reliably
detecting issues like slow progress or deadlocks. We propose a few new metrics that will solve
this issue. Even though KAFKA-5028 will potentially fix existing deadlocks, there will still
be known (and potentially unknown) issues that can cause slow or no progress so these metrics
will still be useful.

KIP:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-143%3A+Additional+Controller+metrics


> Controller Health Metrics (KIP-143)
> -----------------------------------
>
>                 Key: KAFKA-5135
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5135
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Ismael Juma
>            Assignee: Ismael Juma
>             Fix For: 0.11.0.0
>
>
> Ensuring that the Kafka Controller is healthy is an important part of monitoring the
health of a Kafka Cluster. However, the metrics currently exposed are not sufficient for reliably
detecting issues like slow progress or deadlocks. We propose a few new metrics that will solve
this issue. Even though KAFKA-5028 will potentially fix existing deadlocks, there will still
be known (and potentially unknown) issues that can cause slow or no progress so these metrics
will still be useful.
> KIP:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-143%3A+Controller+Health+Metrics



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message