You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/05/05 16:34:04 UTC
[jira] [Updated] (KAFKA-5135) Controller Health Metrics (KIP-143)
[ https://issues.apache.org/jira/browse/KAFKA-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismael Juma updated KAFKA-5135:
-------------------------------
Status: Patch Available (was: Open)
> 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)