[
https://issues.apache.org/jira/browse/KAFKA-8834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934505#comment-16934505
]
Jason Gustafson commented on KAFKA-8834:
----------------------------------------
True, we could report lag from either the leader or the follower's perspective.
I always thought computing on the follower was a little weird since if the
follower failed fetching, then the lag would stay the same. On the other hand,
computing it on the follower makes it easier to know which broker is lagging. I
suppose we could consider doing both.
> Distinguish URPs caused by reassignment plus other metrics
> ----------------------------------------------------------
>
> Key: KAFKA-8834
> URL: https://issues.apache.org/jira/browse/KAFKA-8834
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jason Gustafson
> Assignee: Viktor Somogyi-Vass
> Priority: Major
>
> This Jira tracks implementation of KIP-352:
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-352%3A+Distinguish+URPs+caused+by+reassignment].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
