[ https://issues.apache.org/jira/browse/KAFKA-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ewen Cheslack-Postava resolved KAFKA-3211. ------------------------------------------ Resolution: Fixed Fix Version/s: 0.9.1.0 Issue resolved by pull request 874 [https://github.com/apache/kafka/pull/874] > Handle Connect WorkerTask shutdown before startup correctly > ----------------------------------------------------------- > > Key: KAFKA-3211 > URL: https://issues.apache.org/jira/browse/KAFKA-3211 > Project: Kafka > Issue Type: Bug > Components: copycat > Reporter: Jason Gustafson > Assignee: Jason Gustafson > Fix For: 0.9.1.0 > > > This is a follow-up from KAFKA-3092. The shortcut exit from awaitShutdown() > in WorkerTask can lead to an inconsistent state if the task has not actually > begun execution yet. Although the caller will believe the task has completed > shutdown, nothing stops it from starting afterwards. This could happen if > there is a long delay between the time a task is submitted to an Executor and > the time it begins execution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)