[ https://issues.apache.org/jira/browse/KAFKA-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731403#comment-14731403 ]
Gwen Shapira commented on KAFKA-2510: ------------------------------------- the old data directory will be untouched, but because there are no real errors and everything will appear to be working. New data coming in starting with offset 0, consumers happily consuming this data, and a new __offsets topic. Few hours or days later, when you figured what happened - you are kind of stuck - what are you going to do with the old data directory? > 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)