Home | About | Sematext search-lucene.com search-hadoop.com
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
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> Re: new log.dirs property (as opposed to log.dir)


Copy link to this message
-
Re: new log.dirs property (as opposed to log.dir)
My assumption is that you have something like
  log.dirs=/mnt/diska,/mnt/diskb,/mnt/diskc

Let's say that diskc goes bad. The expected behavior is that the kafka
broker gets an error on write and kills itself.

When that happens you have two options.

Either you remove the drive and add a new one and remount it as /mnt/diskc
(but with no data, just an empty directory). When the broker restarts it
will pull down the data for the partitions that belong on diskc.

Your other option, which you ask about, is to remove /mnt/diskc from the
log.dirs list. If you do this when the broker comes online it will recreate
the partitions it needs but will add them to /mnt/diska and /mnt/diskc
(roughly round-robin).

Hopefully that makes sense.

-Jay
On Thu, Aug 15, 2013 at 11:27 AM, Vadim Keylis <[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