For typical topic creation scenarios: - Replication factor = 3 - min.insync.replicas = 2 - acks = all (ensures not only the leader receives the write, but also the in-sync replicas)
Refer to "min.insync.replicas" section of https://docs.confluent.io/current/installation/configuration/topic-configs.html On Sat, May 4, 2019 at 9:47 PM 15332318...@189.cn <15332318...@189.cn> wrote: > dear: > > Is this a best practice？ > > > From: Erick Lee > Date: 2019-05-05 12:42 > To: users > Subject: Re: kafka loss of data > Hi, > > To prevent data loss within a kafka cluster, it is recommend to set > replication factor to 2/3 with min.insync replica of 2 and acks = all > > Hopefully this article can help provide further insight: > > https://www.confluent.io/blog/3-ways-prepare-disaster-recovery-multi-datacenter-apache-kafka-deployments > > On Sat, May 4, 2019 at 9:21 PM mujvf...@gmail.com <mujvf...@gmail.com> > wrote: > > > dear > > how can I config to ensure that data is lost as little as possible, > > what is the best practice? > > >
