[
https://issues.apache.org/jira/browse/STORM-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
P. Taylor Goetz resolved STORM-424.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.9.3-incubating
Merged.
> 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 (Incubating)
> Issue Type: Bug
> Affects Versions: 0.9.2-incubating
> Reporter: feng xiaojie
> Priority: Minor
> Fix For: 0.9.3-incubating
>
> 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.2#6252)
