[
https://issues.apache.org/jira/browse/STORM-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310924#comment-15310924
]
ASF GitHub Bot commented on STORM-1136:
---------------------------------------
Github user priyank5485 commented on the issue:
https://github.com/apache/storm/pull/1451
@harshach I have renamed Kafka Log Head Offset to Latest Offset, since
Kafka is present in ui header and topic is a column already. I have also
renamed the Query classes as per your suggestion.
Regarding moving it under package tool, I thought of this module specific
to kafka and getting the offset lags. If you are okay with it we can keep it as
is instead of creating a tools package. Or any other suggestion if you have.
Regarding moving getComponentConfiguration to KafkaUtils, KafkaUtils exist
only in the old module. So i will keep it in the spout for now. I plan to add
getComponentConfiguration for trident as well. If there is code duplication
there, I will try to reuse it for old module and new module(when trident is
ready).
Let me know if there is anything else you want me to address. Otherwise I
will squash the commits
> Provide a bin script to check consumer lag from KafkaSpout to Kafka topic
> offsets
> ---------------------------------------------------------------------------------
>
> Key: STORM-1136
> URL: https://issues.apache.org/jira/browse/STORM-1136
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-kafka
> Reporter: Sriharsha Chintalapani
> Assignee: Priyank Shah
>
> We store kafkaspout offsets in zkroot + id path in zookeeper. Kafka provides
> a utility and a protocol request to fetch latest offsets into topic
> {code}
> example:
> bin/kafka-run-classh.sh kafka.tools.GetOffsetTool
> {code}
> we should provide a way for the user to check how far the kafka spout read
> into topic and whats the lag. If we can expose this via UI even better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
