[
https://issues.apache.org/jira/browse/STORM-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Agarwal updated STORM-971:
-----------------------------------
Description: In case of TopicOffsetOutOfRange exception, it is useful to
know just how many unread messages were lost. (was: {noformat}
if (offset < _emittedToOffset - _spoutConfig.maxOffsetBehind) {
LOG.info(
"Skipping failed tuple at offset=" + offset +
" because it's more than maxOffsetBehind=" +
_spoutConfig.maxOffsetBehind +
" behind _emittedToOffset=" + _emittedToOffset
);
}
{noformat}
I believe, having a count metric for skipped messages will help configure the
correct maxOffsetBehind for the topology. Since the skipped messages could
potentially be lost, number is important for the user)
> 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)
