[
https://issues.apache.org/jira/browse/KAFKA-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133461#comment-15133461
]
ASF GitHub Bot commented on KAFKA-3211:
---------------------------------------
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/874
KAFKA-3211: handle WorkerTask stop before start correctly
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka KAFKA-3211
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/874.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #874
----
commit e5a08f53f4a8ca665aae1ea8cb81d11e9ace90ca
Author: Jason Gustafson <ja...@confluent.io>
Date: 2016-02-05T01:16:04Z
KAFKA-3211: handle WorkerTask stop before start correctly
----
> 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
>
> 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)
