[
https://issues.apache.org/jira/browse/KAFKA-15415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Shekhar Narula updated KAFKA-15415:
------------------------------------------
Description: Right now in java-client, producer-batches backoff upto
retry.backoff.ms(100ms by default). This Jira proposes that backoff should be
skipped if in a sub-sequent retry client knows of a newer-leader for the
partition(typically through refresh of parition-metadata via the Metadata RPC).
This would help improve the latency of the produce-request around when
partition leadership changes. (was: Right now in java-client, producer-batches
backoff upto retry.backoff.ms(100ms by default). This Jira proposes that
backoff should be skipped if in a sub-sequent retry, client knows of a
newer-leader for the partition. This would help improve the latency of the
produce-request around leadership changes of a partition.)
> In Java-client, backoff should be skipped for retried producer-batch to a new
> leader
> ------------------------------------------------------------------------------------
>
> Key: KAFKA-15415
> URL: https://issues.apache.org/jira/browse/KAFKA-15415
> Project: Kafka
> Issue Type: Improvement
> Components: clients
> Reporter: Mayank Shekhar Narula
> Assignee: Mayank Shekhar Narula
> Priority: Major
> Fix For: 3.7.0
>
>
> Right now in java-client, producer-batches backoff upto
> retry.backoff.ms(100ms by default). This Jira proposes that backoff should be
> skipped if in a sub-sequent retry client knows of a newer-leader for the
> partition(typically through refresh of parition-metadata via the Metadata
> RPC). This would help improve the latency of the produce-request around when
> partition leadership changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
