You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/09/02 20:55:46 UTC

[jira] [Commented] (KAFKA-2411) remove usage of BlockingChannel in the broker

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

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

Github user asfgit closed the pull request at:

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


> remove usage of BlockingChannel in the broker
> ---------------------------------------------
>
>                 Key: KAFKA-2411
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2411
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: security
>            Reporter: Jun Rao
>            Assignee: Ismael Juma
>            Priority: Blocker
>             Fix For: 0.8.3
>
>
> In KAFKA-1690, we are adding the SSL support at Selector. However, there are still a few places where we use BlockingChannel for inter-broker communication. We need to replace those usage with Selector/NetworkClient to enable inter-broker communication over SSL. Specially, BlockingChannel is currently used in the following places.
> 1. ControllerChannelManager: for the controller to propagate metadata to the brokers.
> 2. KafkaServer: for the broker to send controlled shutdown request to the controller.
> 3. -AbstractFetcherThread: for the follower to fetch data from the leader (through SimpleConsumer)- moved to KAFKA-2440



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