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! On Thu, Jun 13, 2013 at 8:33 AM, Neha Narkhede <[EMAIL PROTECTED]>wrote:
Jonathan Hodges 2013-06-13, 14:36
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext