[ https://issues.apache.org/jira/browse/STORM-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hugo Louro updated STORM-2239: ------------------------------ Component/s: storm-kafka-client > New Kafka spout does not properly handle interrupts > --------------------------------------------------- > > Key: STORM-2239 > URL: https://issues.apache.org/jira/browse/STORM-2239 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka-client > Affects Versions: 2.0.0, 1.1.0 > Reporter: Stig Rohde Døssing > Assignee: Stig Rohde Døssing > Priority: Minor > Fix For: 2.0.0, 1.1.0 > > Time Spent: 2.5h > Remaining Estimate: 0h > > The KafkaConsumer underlying the new Kafka spout had a bug that meant that it > could enter an infinite loop if certain methods were called on it from an > interrupted thread. This can cause local mode clusters to hang on shutdown. > It is fixed in the next Kafka release > (https://issues.apache.org/jira/browse/KAFKA-4387), but a side effect is that > some blocking calls on the consumer can now throw an unchecked > InterruptedException variant. This will cause the executor to crash. The > spout should instead catch the exception if it occurs and set thread > interrupted state before returning control to Storm. -- This message was sent by Atlassian JIRA (v6.4.14#64029)