[KAFKA-13598] idempotence producer is not enabled by default if not set explicitly

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.0, 3.0.0
• Fix Version/s: 3.0.1, 3.2.0, 3.1.1
• Component/s: clients, config
• Assignee: Luke Chen
• Reporter: Luke Chen
• Created: 18/Jan/22 08:53
• Updated: 07/Jun/22 01:23
• Resolved: 07/Feb/22 17:58

Description

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.

Issue Links

• fixes: KAFKA-13589 fix flaky `PlaintextAdminIntegrationTest.testReplicaCanFetchFromLogStartOffsetAfterDeleteRecords` test
• is related to: KAFKA-10619 Enable producer idempotence by default (KIP-679)
• relates to: KAFKA-13673 disable idempotent producer when acks/retries/max.in.flight config conflicts
• links to: GitHub Pull Request #11691
• links to: GitHub Pull Request #11767