I am not super familiar with that code what version of the kafka spout are you using? Is this with Trident or with regular storm?
The code honestly seems over complicated for what it is doing, but I would have to dig more deeply into exactly how the partitions are managed to possibly see why it is doing this. For me though the latest code looks like there is no way what this should happen. https://github.com/apache/storm/blob/master/external/storm-kafka/src/jvm/org/apache/storm/kafka/KafkaSpout.java#L98-L104 But I didn't look a trident. - Bobby On Sunday, March 20, 2016 7:43 AM, Sachin Pasalkar <sachin_pasal...@symantec.com> wrote: Can someone help me out with this? -----Original Message----- From: Sachin Pasalkar [mailto:sachin_pasal...@symantec.com] Sent: Friday, March 18, 2016 9:37 PM To: dev@storm.apache.org Subject: Not enough data to calculate spout lag Hi, I found log "Metrics Tick: Not enough data to calculate spout lag." in my topology and then topology becomes inactive. I check the source: if (_partitions != null && _partitions.size() == _partitionToOffset.size()) { ......}else { LOG.info("Metrics Tick: Not enough data to calculate spout lag."); } What situation will cause _partitions != null or _partitions.size() ==_partitionToOffset.size()? Thanks, Sachin
