ijuma commented on code in PR #19016:
URL: https://github.com/apache/kafka/pull/19016#discussion_r1970582069
##########
clients/src/main/java/org/apache/kafka/common/config/TopicConfig.java:
##########
@@ -172,13 +172,15 @@ public class TopicConfig {
public static final String MIN_IN_SYNC_REPLICAS_CONFIG =
"min.insync.replicas";
public static final String MIN_IN_SYNC_REPLICAS_DOC = "When a producer
sets acks to \"all\" (or \"-1\"), " +
"this configuration specifies the minimum number of replicas that must
acknowledge " +
- "a write for the write to be considered successful. If this minimum
cannot be met, " +
- "then the producer will raise an exception (either NotEnoughReplicas
or " +
- "NotEnoughReplicasAfterAppend).<br>When used together,
<code>min.insync.replicas</code> and <code>acks</code> " +
- "allow you to enforce greater durability guarantees. A typical
scenario would be to " +
- "create a topic with a replication factor of 3, set
<code>min.insync.replicas</code> to 2, and " +
- "produce with <code>acks</code> of \"all\". This will ensure that the
producer raises an exception " +
- "if a majority of replicas do not receive a write.";
+ "a write for the write to be considered successful. If
<code>acks=0</code>, the message may be committed asynchronously; " +
Review Comment:
Do we need to talk about acks=0 or acks=1 here? They are not related to
min.insync.replicas, right?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
