You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/09/26 04:42:05 UTC

[jira] [Updated] (STORM-424) Issue on KafkaOffsetMetric(external/storm-kafka/src/jvm/storm/kafka/KafkaUtils.java)

     [ https://issues.apache.org/jira/browse/STORM-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Kellogg updated STORM-424:
-------------------------------
    Component/s: storm-kafka

> Issue on KafkaOffsetMetric(external/storm-kafka/src/jvm/storm/kafka/KafkaUtils.java)
> ------------------------------------------------------------------------------------
>
>                 Key: STORM-424
>                 URL: https://issues.apache.org/jira/browse/STORM-424
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka
>    Affects Versions: 0.9.2-incubating
>            Reporter: feng xiaojie
>            Priority: Minor
>             Fix For: 0.9.3
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
>  if (latestTimeOffset == 0 || earliestTimeOffset == 0) {
>      LOG.warn("No data found in Kafka Partition " + partition.getId());
>      return null;
> }
> The earliestTimeOffset is 0 by default for a partition, and only after log.retention(segment be deleted), earliestTimeOffset will larger than 0.
> So you will always see the warning, if you run storm-kafka on a new patition, even if there are much data in your partition



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)