[
https://issues.apache.org/jira/browse/STORM-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191789#comment-15191789
]
ASF GitHub Bot commented on STORM-971:
--------------------------------------
GitHub user abhishekagarwal87 opened a pull request:
https://github.com/apache/storm/pull/1208
STORM-971: Metric for messages lost due to kafka retention
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/abhishekagarwal87/storm lostcount
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1208.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1208
----
commit 8c761c5d6d01cdc50db27f144ca361067ffb3ba7
Author: Abhishek Agarwal <abhishek.agar...@inmobi.com>
Date: 2016-03-12T19:07:14Z
STORM-971: Metric for messages lost due to kafka retention
----
> Storm-Kafka: Emit metric for messages lost due to kafka retention
> -----------------------------------------------------------------
>
> Key: STORM-971
> URL: https://issues.apache.org/jira/browse/STORM-971
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-kafka
> Reporter: Abhishek Agarwal
> Assignee: Abhishek Agarwal
>
> In case of TopicOffsetOutOfRange exception, it is useful to know just how
> many unread messages were lost.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
