Hi Patricio, > I set up a 300 ms timeout. Once the timeout occurs, next time I ask for the > iterator from the same strem, I get a:
By timeout, I'm guessing you mean setting consumer.timeout.ms=300. If you do this, it just means that the consumer iterators will shut down if they don't get another set of messages from Kafka within 300 ms. Since the iterators shut down, it is illegal to call hasNext()/next() on the iterators, without recreating them. The way to recreate the iterators is via the createMessageStreams() API in ZookeeperConsumerConnector. Thanks, Neha 2012/1/5 Patricio Echagüe <patric...@gmail.com>: > Hi again. I think I'm running into the Iterator issue mentioned here: > > http://mail-archives.apache.org/mod_mbox/incubator-kafka-users/201201.mbox/%3CCALMKdpuEJfjdo8eHoA-7jGfgp6HhzYiJZRrxLcQCfTK71o%3DgkQ%40mail.gmail.com%3E > > I set up a 300 ms timeout. Once the timeout occurs, next time I ask for the > iterator from the same strem, I get a: > > java.lang.IllegalStateException: Iterator is in failed state > > at kafka.utils.IteratorTemplate.hasNext(IteratorTemplate.scala:47) > > at com.lucid.dao.queue.impl.kafka.KafkaConsumerIterator.hasNext( > KafkaConsumerIterator.java:21) > > ..... > > ..... > > Note: I'm using the latest Kafka release. > > Any suggestion ? > > Thanks
