[
https://issues.apache.org/jira/browse/KAFKA-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753849#comment-16753849
]
Sönke Liebau commented on KAFKA-1021:
-------------------------------------
Is this tool still necessary? From the wording in the issue above this sounds a
little like this was before min.insync.isr and the unclean leader election
configs..
> Write a tool to check replica lag for individual topic partitions
> -----------------------------------------------------------------
>
> Key: KAFKA-1021
> URL: https://issues.apache.org/jira/browse/KAFKA-1021
> Project: Kafka
> Issue Type: Improvement
> Components: tools
> Affects Versions: 0.8.0
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
> Priority: Major
>
> For highest consistency guarantees, we require all replicas to be in-sync
> with the leader. This increases the possibility of picking an in-sync replica
> as the next leader, during leader election. However, due to network/disk/CPU
> bottleneck, replicas may fall out of ISR. One of the first things to check is
> if the replica is making progress and how many messages behind it has fallen.
> We need a simple tool that can take in one or more topics/partitions and find
> the lag of the replicas. This tool is similar in usage to the
> ConsumerOffsetChecker, but work differently since we do not checkpoint
> replica offsets in zookeeper.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
