You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Manikumar (JIRA)" <ji...@apache.org> on 2018/04/12 14:30:00 UTC

[jira] [Resolved] (KAFKA-4124) Handle disk failures gracefully

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

Manikumar resolved KAFKA-4124.
------------------------------
    Resolution: Duplicate

Some of these requirements are implemented in KIP-112/KIP-113. Pls raise new JIRAs for any missing/additional requirements/improvements.

> Handle disk failures gracefully
> -------------------------------
>
>                 Key: KAFKA-4124
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4124
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Gokul
>            Priority: Major
>
> Currently when a disk goes down, the broker also goes down with it. This causes too much reshuffle of data over the network to replace the broker. Make the broker resilient to disk failure. 
> The broker can detect a disk failure, mark it bad and then re-replicate the under replicated data in all other available disks in the node. If the bad disk is replaced with new one, the broker can rebalance the data among all other disks it has. The broker can also tolerate upto n disk failures.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)