[KAFKA-2411] remove usage of BlockingChannel in the broker

• Type: Sub-task
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 0.9.0.0
• Component/s: security
• Assignee: Ismael Juma
• Reporter: Jun Rao
• Created: 05/Aug/15 23:22
• Updated: 02/Sep/15 18:55
• Resolved: 02/Sep/15 18:55

Description

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

Issue Links

• blocks: KAFKA-2072 Add StopReplica request/response to o.a.k.common.requests and replace the usage in core module
• duplicates: KAFKA-2074 Add UpdateMetadata request/response to o.a.k.common.requests