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 >> 0.8 Durability Question


Copy link to this message
-
Re: 0.8 Durability Question
No. It only means that messages are written to all replicas in memory. Data
is flushed to disk asynchronously.

Thanks,
Neha
On Jun 13, 2013 3:29 AM, "Jonathan Hodges" <[EMAIL PROTECTED]> wrote:

> Looking at Jun’s ApacheCon slides (
> http://www.slideshare.net/junrao/kafka-replication-apachecon2013) slide 21
> titled, ‘Data Flow in Replication’ there are three possible durability
> configurations which tradeoff latency for greater persistence guarantees.
>
> The third row is the ‘no data loss’ configuration option where the producer
> only receives an ack from the broker once the message(s) are committed by
> the leader and peers.  Does this commit also mean the message(s) are
> flushed to disk?  I know there is a separate configuration setting,
> log.flush.interval.messages, but I thought in sync mode the producer
> doesn’t receive an ack until message(s) are committed and flushed to disk.
>  Please correct me if my understanding is incorrect.
>
> Thanks,
> Jonathan
>

 
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