[ 
https://issues.apache.org/jira/browse/KAFKA-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jun Rao updated KAFKA-612:
--------------------------

       Resolution: Fixed
    Fix Version/s: 0.8
           Status: Resolved  (was: Patch Available)

Thanks for the review. Changed the method name and committed to 0.8.
                
> move shutting down of fetcher thread out of critical path
> ---------------------------------------------------------
>
>                 Key: KAFKA-612
>                 URL: https://issues.apache.org/jira/browse/KAFKA-612
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>             Fix For: 0.8
>
>         Attachments: kafka-612.patch, kafka-612-v2.patch
>
>
> Shutting down a fetch thread seems to take more than 200ms since we need to 
> interrupt the thread. Currently, we shutdown fetcher threads while processing 
> a leaderAndIsr request. This can delay some of the partitions to become a 
> leader.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to