kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manikumar (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-6263) Expose metric for group metadata loading duration
Date Mon, 07 Oct 2019 17:19:00 GMT

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

Manikumar resolved KAFKA-6263.
------------------------------
    Fix Version/s: 2.4.0
       Resolution: Fixed

> Expose metric for group metadata loading duration
> -------------------------------------------------
>
>                 Key: KAFKA-6263
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6263
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jason Gustafson
>            Assignee: Anastasia Vela
>            Priority: Major
>             Fix For: 2.4.0
>
>
> We have seen in several cases where the log cleaner either wasn't enabled or had experienced
some failure that __consumer_offsets partitions can grow excessively. When one of these partitions
changes leadership, the new coordinator must load the offset cache from the start of the log,
which can take arbitrarily long depending on how large the partition has grown (we have seen
cases where it took hours). Catching this problem is not always easy because the condition
is rare and the symptom just tends to be a long period of inactivity in the consumer group
which gradually gets worse over time. It may therefore be useful to have a broker metric for
the load time so that it can be monitored and potentially alerted on. Same thing goes for
the transaction log 



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

Mime
View raw message