Ming Liu created KAFKA-12713:
--------------------------------
Summary: Report broker/consumer fetch latency more accurately
Key: KAFKA-12713
URL: https://issues.apache.org/jira/browse/KAFKA-12713
Project: Kafka
Issue Type: Bug
Reporter: Ming Liu
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)
