kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neha Narkhede (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-50) kafka intra-cluster replication support
Date Thu, 01 Mar 2012 21:59:59 GMT

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

Neha Narkhede commented on KAFKA-50:
------------------------------------

Cool, so I was thinking if the original design was on a wiki too, it will be much easier to
point to sections of it, to make discussions easier. If you have a text copy of it, would
you mind pasting it in a Kafka JIRA page ? It would be very useful.
                
> kafka intra-cluster replication support
> ---------------------------------------
>
>                 Key: KAFKA-50
>                 URL: https://issues.apache.org/jira/browse/KAFKA-50
>             Project: Kafka
>          Issue Type: New Feature
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>             Fix For: 0.8
>
>         Attachments: kafka_replication_detailed_design_v2.pdf, kafka_replication_highlevel_design.pdf,
kafka_replication_lowlevel_design.pdf
>
>
> Currently, Kafka doesn't have replication. Each log segment is stored in a single broker.
This limits both the availability and the durability of Kafka. If a broker goes down, all
log segments stored on that broker become unavailable to consumers. If a broker dies permanently
(e.g., disk failure), all unconsumed data on that node is lost forever. Our goal is to replicate
every log segment to multiple broker nodes to improve both the availability and the durability.

> We'd like to support the following in Kafka replication: 
> 1. Configurable synchronous and asynchronous replication 
> 2. Small unavailable window (e.g., less than 5 seconds) during broker failures 
> 3. Auto recovery when a failed broker rejoins 
> 4. Balanced load when a broker fails (i.e., the load on the failed broker is evenly spread
among multiple surviving brokers)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message