[
https://issues.apache.org/jira/browse/KAFKA-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925694#comment-17925694
]
David Jacot commented on KAFKA-18762:
-------------------------------------
acks = all works as expected in this case. acks = all means that the produce
must wait for the write to be replicated to all the replicas within the ISR. As
there is one replica, there is only one replica in the ISR. Hence writing
locally is enough.
That being said, I agree that we could improve the configuration. I supposed
that we didn’t do it in the past because of the path that Jun mentioned.
> 'Acks=all' not working correctly in Kafka Kraft mode.
> -----------------------------------------------------
>
> Key: KAFKA-18762
> URL: https://issues.apache.org/jira/browse/KAFKA-18762
> Project: Kafka
> Issue Type: Bug
> Components: kraft
> Affects Versions: 3.9.0
> Reporter: Shubham Raj
> Priority: Critical
>
> In Kraft mode, producers are able to produce messages to a topic with a
> replication factor of 1, even when the {{min.insync.replicas}} setting is 2
> and {{{}acks=all{}}}. This behavior is inconsistent with Zookeeper mode,
> where the production fails with a timeout exception as expected. This was
> observed in Kafka 3.9.0. We tried both Java and Python API.
>
> *Steps to Reproduce:*
> # Set up a Kafka cluster in Kraft mode.
> # Create a topic with the following properties:
> ** Replication Factor: 1
> ** Partitions: 1 (for simplicity)
> # Set the {{min.insync.replicas}} configuration for the cluster to 2.
> # Configure a Kafka producer with {{{}acks=all{}}}.
> # Attempt to produce messages to the topic.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
