[
https://issues.apache.org/jira/browse/KAFKA-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679544#comment-14679544
]
Jun Rao commented on KAFKA-2411:
--------------------------------
[~sriharsha], I wasn't thinking of replacing blocking channel with network
client. Blocking channel is used by the old clients which will be deprecated in
the future and is also tied to the scala request objects which will also be
deprecated. It seems that it's simpler to replace the places that we use
BlockingChannel in the broker with either Selector or NetworkClient. If it's
the latter, we need to somehow decouple the metadata update part from
NetworkClient since it's not relevant.
> 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
>
> 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).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
