kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Lee <er...@confluent.io>
Subject Re: Re: kafka loss of data
Date Sun, 05 May 2019 05:00:02 GMT
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 15332318109@189.cn <15332318109@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 mujvf887@gmail.com <mujvf887@gmail.com>
> wrote:
>
> > dear
> >  how can I config to ensure that data is lost as little as possible,
> > what is the best practice?
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message