kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Onur Karaman (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (KAFKA-5027) Kafka Controller Redesign
Date Thu, 07 Sep 2017 01:16:00 GMT

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

Onur Karaman edited comment on KAFKA-5027 at 9/7/17 1:15 AM:
-------------------------------------------------------------

I think we'd want all the broker components communicating with zookeeper migrated to the new
client, so that would be:
KAFKA-5642
KAFKA-5645
KAFKA-5646
KAFKA-5647

At the bare minimum, we'd have KAFKA-5642 and KAFKA-5646 checked in.


was (Author: onurkaraman):
I think we'd want all the broker components communicating with zookeeper migrated to the new
client, so that would be:
KAFKA-5642
KAFKA-5645
KAFKA-5646
KAFKA-5647

> Kafka Controller Redesign
> -------------------------
>
>                 Key: KAFKA-5027
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5027
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Onur Karaman
>            Assignee: Onur Karaman
>
> The goal of this redesign is to improve controller performance, controller maintainability,
and cluster reliability.
> Documentation regarding what's being considered can be found [here|https://docs.google.com/document/d/1rLDmzDOGQQeSiMANP0rC2RYp_L7nUGHzFD9MQISgXYM].



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message