You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Gwen Shapira (JIRA)" <ji...@apache.org> on 2015/09/03 19:07:45 UTC

[jira] [Created] (KAFKA-2510) Prevent broker from re-replicating / losing data due to disk misconfiguration

Gwen Shapira created KAFKA-2510:
-----------------------------------

             Summary: Prevent broker from re-replicating / losing data due to disk misconfiguration
                 Key: KAFKA-2510
                 URL: https://issues.apache.org/jira/browse/KAFKA-2510
             Project: Kafka
          Issue Type: Bug
            Reporter: Gwen Shapira


Currently Kafka assumes that whatever it sees in the data directory is the correct state of the data.

This means that if an admin mistakenly configures Chef to use wrong data directory, one of the following can happen:
1. The broker will replicate a bunch of partitions and take over the network
2. If you did this to enough brokers, you can lose entire topics and partitions.

We have information about existing topics, partitions and their ISR in zookeeper.

We need a mode in which if a broker starts, is in ISR for a partition and doesn't have any data or directory for the partition, the broker will issue a huge ERROR in the log and refuse to do anything for the partition.

[~fpj] worked on the problem for ZK and had some ideas on what is required here. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)