You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Kai Huang (Jira)" <ji...@apache.org> on 2021/07/29 19:25:00 UTC

[jira] [Assigned] (KAFKA-12713) Report "REAL" follower/consumer fetch latency

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

Kai Huang reassigned KAFKA-12713:
---------------------------------

    Assignee: Kai Huang

> Report "REAL" follower/consumer fetch latency
> ---------------------------------------------
>
>                 Key: KAFKA-12713
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12713
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Ming Liu
>            Assignee: Kai Huang
>            Priority: Major
>
> The fetch latency is an important metrics to monitor for the cluster performance. With ACK=ALL, the produce latency is affected primarily by broker fetch latency.
> However, currently the reported fetch latency didn't reflect the true fetch latency because it sometimes need to stay in purgatory and wait for replica.fetch.wait.max.ms when data is not available. This greatly affect the real P50, P99 etc. 
> I like to propose a KIP to be able track the real fetch latency for both broker follower and consumer. 
>  



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