[ 
https://issues.apache.org/jira/browse/KAFKA-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730369#comment-15730369
 ] 

ASF GitHub Bot commented on KAFKA-4510:
---------------------------------------

GitHub user mjsax opened a pull request:

    https://github.com/apache/kafka/pull/2227

    KAFKA-4510: StreamThread must finish rebalance in state PENDING_SHUTDOWN

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mjsax/kafka 
kafka-4510-finish-rebalance-on-shutdown

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/2227.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 #2227
    
----
commit 1568713abe7bd95495f673d507f96812484efcc8
Author: Matthias J. Sax <matth...@confluent.io>
Date:   2016-12-07T23:55:36Z

    KAFKA-4510: StreamThread must finish rebalance in state PENDING_SHUTDOWN

----


> StreamThread must finish rebalance in state PENDING_SHUTDOWN
> ------------------------------------------------------------
>
>                 Key: KAFKA-4510
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4510
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>            Reporter: Matthias J. Sax
>            Assignee: Matthias J. Sax
>
> If a Streams application runs with multiple threads within one JVM and the 
> application gets stopped. this can triggers a rebalance when the first 
> threads finishes processing because not all thread shut down at the same time.
> Because we try to reuse tasks, on rebalance task are not closed immediately 
> in order for a potential reuse (if a task gets assigned the its original 
> thread). However, if a thread is in state {{PENDING_SHUTDOWN}} it does finish 
> the rebalance operation completely and thus does not release the suspended 
> task and the application exits with not all locks released.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to