Possibly update Kafka-related doc about enable.idempotence
default change by Kafka
#7189
Labels
Milestone
enable.idempotence
default change by Kafka
#7189
Environment Details
Problem Description
Kafka has changed the default value of
enable.idempotence
fromfalse
totrue
between (seemingly) releases 3.0 and 3.0.1. This can cause the Kafka errorExplicitly setting
enable.idempotence
tofalse
avoids this problem.We might consider updating our messaging doc to alert users to this.
But, that can lead to another related error:
Because the default timeout value has also changed, apparently from 10000 to 45000.
Explicitly configuring the value to 10000 works around this second issue.
The
enable.idempotence
issue was reported on our internal Slack channel and as well by other platforms: https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.6-Release-Notes#kafka-30The text was updated successfully, but these errors were encountered: