The acks setting for the producer doesn't affect the final durability guarantees. These are still enforced by the replication and min ISR settings. Instead, the ack setting just lets the producer control how durable the write is before *that producer* can consider the write "complete", i.e. before it gets an ack.
-Ewen On Tue, Jan 24, 2017 at 12:46 PM, Luciano Afranllie < listas.luaf...@gmail.com> wrote: > Hi everybody > > I am trying to understand why Kafka let each individual producer, on a > connection per connection basis, choose the tradeoff between availability > and durability, honoring min.insync.replicas value only if producer uses > ack=all. > > I mean, for a single topic, cluster administrators can't enforce messages > to be stores in a minimum number of replicas without coordinating with all > producers to that topic so all of them use ack=all. > > Is there something that I am missing? Is there any other strategy to > overcome this situation? > > Regards > Luciano >
