If you get a disk error that results in an IOException the broker will shut itself down. You would then have the option of replacing the disk or deleting that data directory from the list. When the broker is brought back up the intact partitions will quickly catch up and be online; the destroyed partitions will have to fully rebuild off the other replicas and will take a little longer but will automatically come back online once they have restored off the replicas.


Sent from my iPhone

On Aug 14, 2013, at 1:49 PM, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB