Kafka, mail # dev - Re: Segment recovery and replication - 2013-08-29, 15:44
 Search Hadoop and all its subprojects:

Switch to Threaded View
Copy link to this message
-
Re: Segment recovery and replication
This should not happen. We have a notion of a "committed" message, which is
a message present on all "in sync" nodes. We never hand out a  message to
any consumer until it is committed, and we guarantee that only "in sync"
nodes are electable as leaders. Setting acks=-1 means wait until the
message is committed before returning to the producer.

If you kill all nodes however then all bets are off. In this case we will
elect whichever node shows up first as leader and use its log as the source
of truth. Is it possible this is happening?

-Jay
On Thu, Aug 29, 2013 at 8:32 AM, Sam Meder <[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