Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-50

kafka intra-cluster replication support

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.8.0
    • None
    • None

    Description

      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)

      Here is a complete design proposal for Kafka replication - https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Replication

      Attachments

        Issue Links

        incorporates

        Bug - A problem which impairs or prevents the functions of the product. KAFKA-352 Throw exception to client if it makes a produce/consume request to a Kafka broker for a topic that hasn't been created

        • Major - Major loss of function.
        • Resolved
        is blocked by

        Bug - A problem which impairs or prevents the functions of the product. KAFKA-41 multi-produce and multi-fetch support with replication

        • Major - Major loss of function.
        • Resolved

        Bug - A problem which impairs or prevents the functions of the product. KAFKA-44 Various ZK listeners to support intra-cluster replication

        • Major - Major loss of function.
        • Resolved

        Bug - A problem which impairs or prevents the functions of the product. KAFKA-45 Broker startup, leader election, becoming a leader/follower for intra-cluster replication

        • Major - Major loss of function.
        • Resolved

        Bug - A problem which impairs or prevents the functions of the product. KAFKA-46 Commit thread, ReplicaFetcherThread for intra-cluster replication

        • Major - Major loss of function.
        • Resolved

        Bug - A problem which impairs or prevents the functions of the product. KAFKA-47 Create topic support and new ZK data structures for intra-cluster replication

        • Major - Major loss of function.
        • Resolved

        Bug - A problem which impairs or prevents the functions of the product. KAFKA-48 Implement optional "long poll" support in fetch request

        • Major - Major loss of function.
        • Resolved

        Bug - A problem which impairs or prevents the functions of the product. KAFKA-49 Add acknowledgement to the produce request.

        • Major - Major loss of function.
        • Resolved

        Bug - A problem which impairs or prevents the functions of the product. KAFKA-42 Support rebalancing the partitions with replication

        • Blocker - Blocks development and/or testing work, production could not run
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. KAFKA-43 Rebalance to preferred broke with intra-cluster replication support

        • Blocker - Blocks development and/or testing work, production could not run
        • Closed

        New Feature - A new feature of the product, which has yet to be developed. KAFKA-174 Add performance suite for Kafka

        • Major - Major loss of function.
        • Resolved

        New Feature - A new feature of the product, which has yet to be developed. KAFKA-330 Add delete topic support

        • Blocker - Blocks development and/or testing work, production could not run
        • Closed

        Improvement - An improvement or enhancement to an existing feature or task. KAFKA-327 Monitoring and tooling for Kafka replication

        • Critical - Crashes, loss of data, severe memory leak.
        • Resolved

        Improvement - An improvement or enhancement to an existing feature or task. KAFKA-252 Generalize getOffsetsBefore API to a new more general API getLeaderMetadata

        • Major - Major loss of function.
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            junrao Jun Rao
            junrao Jun Rao
            Votes:
            3 Vote for this issue
            Watchers:
            23 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 1,764h
              1,764h
              Remaining:
              Remaining Estimate - 1,764h
              1,764h
              Logged:
              Time Spent - Not Specified
              Not Specified

              Slack

                Issue deployment