Thank you Gwen for the reply. Is there a way that I can prevent data duplication upon receiving NOT_ENOUGH_REPLICAS_AFTER_APPEND error?
On Tue, 9 Jun 2015 at 00:27 Gwen Shapira <gshap...@cloudera.com> wrote: > Hi, > > What you said is exactly correct :) > > We check ISR size twice. Once before writing to leader, and once when > checking for acks. The first error is thrown if we detect a small ISR > before writing to the leader. The second if the ISR shrank after we > wrote to the leader but before we got enough acks. > > Gwen > > On Mon, Jun 8, 2015 at 2:51 AM, tao xiao <xiaotao...@gmail.com> wrote: > > Hi team, > > > > What is the difference between producer error NOT_ENOUGH_REPLICAS and > > NOT_ENOUGH_REPLICAS_AFTER_APPEND? Does the later one imply that the > message > > has been written to the leader log successfully? If I have retry turned > on > > in producer does it mean that duplicated messages may be written to > broker > > when NOT_ENOUGH_REPLICAS_AFTER_APPEND is encountered? >
