[
https://issues.apache.org/jira/browse/KAFKA-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546397#comment-13546397
]
Jun Rao commented on KAFKA-685:
-------------------------------
Thanks for the patch. The code looks good. Got the following error on latest
0.8 branch. This is likely due to the recent change in KAFKA-668. So you need
to change the regex a bit.
ERROR Could not parse broker info Some(jrao-ld.linkedin.biz:9092:9999) with
regex ^([^:]+):(\d+)$ (kafka.tools.ConsumerOffsetChecker$)
> ConsoleOffsetChecker does not work with 0.8
> -------------------------------------------
>
> Key: KAFKA-685
> URL: https://issues.apache.org/jira/browse/KAFKA-685
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8
> Reporter: Maxime Brugidou
> Attachments: KAFKA-685.patch
>
>
> The ConsoleOffsetChecker does not work anymore with 0.8, this tool is very
> useful when used with the MirrorMaker.
> Here is a patch to make it work with some cosmetic changes:
> * script-friendly formatting (one line per partition)
> * offsets do not correspond to bytes anymore (so the lag is in number of
> messages, not GiB)
> * --broker-info optional option to print the broker list at the end (like the
> previous version)
> Example:
> bin/kafka-run-class.sh kafka.tools.ConsumerOffsetChecker --group KafkaMirror
> --zkconnect zoo.example.org:2181
> Group Topic Pid Offset logSize Lag
> Owner
> KafkaMirror test 0 215385 215385 0
> Some(KafkaMirror_broker01-1379350-71cf9117-0)
> KafkaMirror test 1 683564 683564 0
> Some(KafkaMirror_broker03-1379351-71cf9117-0)
> KafkaMirror test2 0 176943 176943 0
> Some(KafkaMirror_broker05-1379353-71cf91
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
