[
https://issues.apache.org/jira/browse/KAFKA-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659184#comment-14659184
]
Jun Rao commented on KAFKA-2411:
--------------------------------
For AbstractFetcherThread, we could potentially use NetworkClient. However, we
need to be a bit careful since the follower fetcher thread doesn't need to
refresh metadata itself. Instead, the information about the leader is
propagated from the controller.
> 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
>
> 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)
