You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Mayank Shekhar Narula (Jira)" <ji...@apache.org> on 2023/11/14 16:23:00 UTC

[jira] [Updated] (KAFKA-15824) SubscriptionState's maybeValidatePositionForCurrentLeader should handle partition which isn't subscribed yet

     [ https://issues.apache.org/jira/browse/KAFKA-15824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mayank Shekhar Narula updated KAFKA-15824:
------------------------------------------
    Issue Type: Bug  (was: Improvement)

> SubscriptionState's maybeValidatePositionForCurrentLeader should handle partition which isn't subscribed yet
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-15824
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15824
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>            Reporter: Mayank Shekhar Narula
>            Assignee: Mayank Shekhar Narula
>            Priority: Major
>             Fix For: 3.7.0, 3.6.1
>
>
> Right now in java-client, producer-batches backoff upto retry.backoff.ms(100ms by default). This Jira proposes that backoff should be skipped if client knows of a newer-leader for the partition in a sub-sequent retry(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)