You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Federico Valeri (Jira)" <ji...@apache.org> on 2024/11/04 14:54:00 UTC
[jira] [Comment Edited] (KAFKA-17926) Improve the documentation explaining why max.in.flight.requests.per.connection should not exceed 5.
[ https://issues.apache.org/jira/browse/KAFKA-17926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895313#comment-17895313 ]
Federico Valeri edited comment on KAFKA-17926 at 11/4/24 2:53 PM:
------------------------------------------------------------------
> If users configure `max.in.flight.requests.per.connection>5`, the idempotent will be disabled
Yes, but that's not the default configuration, as the user changed max.in.flight.requests.per.connection. Are you suggesting that idempotent should be the only option available?
was (Author: fvaleri):
> If users configure `max.in.flight.requests.per.connection>5`, the idempotent will be disabled
Yes, but that's not the default configuration, as used changed max.in.flight.requests.per.connection. Are you suggesting that idempotent should be the only option available?
> 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)