[
https://issues.apache.org/jira/browse/STORM-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311357#comment-15311357
]
ASF GitHub Bot commented on STORM-1136:
---------------------------------------
Github user harshach commented on the issue:
https://github.com/apache/storm/pull/1451
@priyank5485 I overlooked that this code is in external/module we can keep
the classes as it is. My comment regarding getComponentConfiguration as it
looks to be doing bit of logic in KafkaSpout and my suggestion was to move that
code to KafkaUtils and call buildKafkaSpoutComponentConfig and return the
config map . This way spout code looks cleaner and may be
buildKafkaSpoutComponentConfig can be reused for trident.
Go ahead with you commit squashes and you can add me to sponsor list since
its in external module
> 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)
