[ https://issues.apache.org/jira/browse/KAFKA-17926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895258#comment-17895258 ]
Chia-Ping Tsai commented on KAFKA-17926: ---------------------------------------- {quote} isn't that already the case since 3.0? Just for my understanding. {quote} If users configure `max.in.flight.requests.per.connection>5`, the idempotent will be disabled. see https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/producer/ProducerConfig.java#L591 > Improve the documentation explaining why > max.in.flight.requests.per.connection should not exceed 5. > --------------------------------------------------------------------------------------------------- > > Key: KAFKA-17926 > URL: https://issues.apache.org/jira/browse/KAFKA-17926 > Project: Kafka > Issue Type: Improvement > Reporter: Chia-Ping Tsai > Assignee: PoAn Yang > Priority: Minor > > We should highlight that the server [0] retains record metadata for the 5 > most recent batches, so sending too many requests to a node simultaneously > can break idempotence. > [0] > https://github.com/apache/kafka/blob/af53758746485daa06c4d4366036c04f7f9f0e63/storage/src/main/java/org/apache/kafka/storage/internals/log/ProducerStateEntry.java#L32 -- This message was sent by Atlassian Jira (v8.20.10#820010)