kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-2411) remove usage of BlockingChannel in the broker
Date Fri, 28 Aug 2015 23:51:45 GMT

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

Ismael Juma updated KAFKA-2411:
    Status: Patch Available  (was: In Progress)

I've updated the PR to use `NetworkClient` instead of `Selector`. This turned out to require
adding various new requests in `Protocol`. There are a couple of things, in particular, that
would be good to get feedback on:

* How metadata updates were moved to the `MetadataUpdater` interface.
* The implementation of the methods in `NetworkClientBlockingOps`.

Any other feedback is welcome, of course.

> 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
>             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

View raw message