[
https://issues.apache.org/jira/browse/KAFKA-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925619#comment-17925619
]
PoAn Yang commented on KAFKA-18762:
-----------------------------------
> How can we stop a Kafka user to not create a topic with replication factor <
> min insync replica ?
For a new topic, we may add validation to
ReplicationControlManager#createTopics.
For dynamic config change, we can probably add validation to
https://github.com/apache/kafka/blob/e53af1a48974926d2e671b2d02f6bedf0394d3d6/core/src/main/scala/kafka/server/ConfigAdminManager.scala#L239-L251.
> '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)
