Breaking News: Grepper is joining You.com. Read the official announcement!
Check it out

Minimum in-sync replicas#

Sumit Rawal answered on June 1, 2023 Popularity 3/10 Helpfulness 1/10

Contents


More Related Answers

  • kubectl scale --replicas to 0
  • read replicas
  • in sync replica
  • Read replica#
  • Why use read replicas?#
  • Geographically distributed replicas#

  • Minimum in-sync replicas#

    0

    We have learnt that a producer can write messages to a topic partition and the messages are declared committed as long as all the in-sync replicas receive and write the message (as per Kafka reliability guarantees). However, if there’s only one in-sync replica (the leader), data loss and inconsistency can occur if the only in-sync replica goes down and is replaced by an out of sync replica as the new leader. We can protect from such a situation by configuring the parameter min.insync.replicas, which sets the minimum number of replicas to be in-sync before a message can be processed. Say, if we have 3 replicas and the parameter min.insync.replicas is set to 2, then a producer attempting to write a message to the topic will be met with NotEnoughReplicasException exception in case two out of the three replicas are down. In this situation, the single in-sync replica becomes read-only and continues to serve consumers.

    Popularity 3/10 Helpfulness 1/10 Language whatever
    Source: Grepper
    Link to this answer
    Share Copy Link
    Contributed on Jun 01 2023
    Sumit Rawal
    0 Answers  Avg Quality 2/10


    X

    Continue with Google

    By continuing, I agree that I have read and agree to Greppers's Terms of Service and Privacy Policy.
    X
    Grepper Account Login Required

    Oops, You will need to install Grepper and log-in to perform this action.