[jira] [Updated] (KAFKA-16083) Exclude throttle time when expiring inflight requests on a connection
[ https://issues.apache.org/jira/browse/KAFKA-16083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adithya Chandra updated KAFKA-16083: Affects Version/s: (was: 3.7.0) > Exclude throttle time when expiring inflight requests on a connection > - > > Key: KAFKA-16083 > URL: https://issues.apache.org/jira/browse/KAFKA-16083 > Project: Kafka > Issue Type: Bug > Components: clients >Reporter: Adithya Chandra >Priority: Critical > Fix For: 3.8.0 > > > When expiring inflight requests, the network client does not take throttle > time into account. If a connection has multiple inflight requests (default of > 5) and each request is throttled then some of the requests can incorrectly > marked as expired. Subsequently the connection is closed and the client > establishes a new connection to the broker. This behavior leads to > unnecessary connections to the broker, leads to connection storms and > increases latencies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-16083) Exclude throttle time when expiring inflight requests on a connection
[ https://issues.apache.org/jira/browse/KAFKA-16083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adithya Chandra updated KAFKA-16083: Affects Version/s: 3.7.0 > Exclude throttle time when expiring inflight requests on a connection > - > > Key: KAFKA-16083 > URL: https://issues.apache.org/jira/browse/KAFKA-16083 > Project: Kafka > Issue Type: Bug > Components: clients >Affects Versions: 3.7.0 >Reporter: Adithya Chandra >Priority: Critical > Fix For: 3.8.0 > > > When expiring inflight requests, the network client does not take throttle > time into account. If a connection has multiple inflight requests (default of > 5) and each request is throttled then some of the requests can incorrectly > marked as expired. Subsequently the connection is closed and the client > establishes a new connection to the broker. This behavior leads to > unnecessary connections to the broker, leads to connection storms and > increases latencies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
