[ https://issues.apache.org/jira/browse/KAFKA-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17547803#comment-17547803 ]
Derek Troy-West edited comment on KAFKA-13598 at 6/4/22 2:02 AM: ----------------------------------------------------------------- This represents a breaking change where: # Broker version is < 2.8.0 # Cluster has ACL configured, but no IDEMPOTENT_WRITE permission set # Producer has default configuration (or no config captured in KAFKA-13673) # Kafka Client library version is bumped to 3.2.0 in the producing application The resulting production error has a ClusterAuthorizationException but it wasn't clear that a new ACL was required until we found KAFKA-13759. I think 1-3 might be quite a common scenario for Kafka users in the wild, and 4 is very easy to do on the application side. Perhaps it might be an idea to add a note to the 3.2.0 upgrade guide or release notes about this one. More info: [https://kpow.io/articles/kafka-producer-breaking-change/] was (Author: d-t-w): This represents a breaking change where: # Broker version is < 2.8.0 # Cluster has ACL configured, but no IDEMPOTENT_WRITE permission set # Producer has default configuration (or no config captured in KAFKA-13673) # Kafka Client library version is bumped to 3.2.0 The resulting production error has a ClusterAuthorizationException but it wasn't clear that a new ACL was required until we found KAFKA-13759. I think 1-3 might be quite a common scenario for Kafka users in the wild, and 4 is very easy to do on the application side. Perhaps it might be an idea to add a note to the 3.2.0 upgrade guide or release notes about this one. More info: https://kpow.io/articles/kafka-producer-breaking-change/ > idempotence producer is not enabled by default if not set explicitly > -------------------------------------------------------------------- > > Key: KAFKA-13598 > URL: https://issues.apache.org/jira/browse/KAFKA-13598 > Project: Kafka > Issue Type: Bug > Components: clients, config > Affects Versions: 3.1.0, 3.0.0 > Reporter: Luke Chen > Assignee: Luke Chen > Priority: Major > Fix For: 3.0.1, 3.2.0, 3.1.1 > > > In KAFKA-10619, we intended to enable idempotence by default, but this was > not achieved due to a bug in the config validation logic. The change from > acks=1 to acks=all worked correctly, however. > This is the following up for KIP-679: > [https://cwiki.apache.org/confluence/display/KAFKA/KIP-679%3A+Producer+will+enable+the+strongest+delivery+guarantee+by+default] > > Note: In KAFKA-13673, we'll disable idempotent producer when > acks/retries/max.in.flight config conflicts, to avoid breaking existing > producers. -- This message was sent by Atlassian Jira (v8.20.7#820007)