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.