Hello, We have been running our pre-production with Storm 1.2.0 preview + Storm Kafka client 1.2.0 preview (shared by Stig Dosing, see the [Discuss] Release 1.2.0 topic in this mailing list).
My team member Ronan Harmenies noticed the following exception thrown by the Storm Kafka spout: java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442) at java.util.HashMap$KeyIterator.next(HashMap.java:1466) at org.apache.storm.kafka.spout.KafkaSpout.doSeekRetriableTopicPartitions(KafkaSpout.java:347) at org.apache.storm.kafka.spout.KafkaSpout.pollKafkaBroker(KafkaSpout.java:320) at org.apache.storm.kafka.spout.KafkaSpout.nextTuple(KafkaSpout.java:245) at org.apache.storm.daemon.executor$fn__4963$fn__4978$fn__5009.invoke(executor.clj:647) at org.apache.storm.util$async_loop$fn__557.invoke(util.clj:484) at clojure.lang.AFn.run(AFn.java:22) at java.lang.Thread.run(Thread.java:748) Looks like there's something to fix here, like making the map thread-safe, or managing the exclusivity of modification of this map at a caller level. Should I fill a JIRA to make sure this is tracked ? Best regards, Alexandre Vermeerbergen
