[
https://issues.apache.org/jira/browse/KAFKA-15824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Shekhar Narula updated KAFKA-15824:
------------------------------------------
Description: As can be seen
[here|[https://github.com/apache/kafka/blob/832627fc78484fdc7c8d6da8a2d20e7691dbf882/clients/src/main/java/org/apache/kafka/clients/consumer/internals/SubscriptionState.java#L453]],
it doesn't check if partition is subscribed by checking TopicPartitionState
cached is null or not, as done here by maybe (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 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.)
> 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
>
>
> As can be seen
> [here|[https://github.com/apache/kafka/blob/832627fc78484fdc7c8d6da8a2d20e7691dbf882/clients/src/main/java/org/apache/kafka/clients/consumer/internals/SubscriptionState.java#L453]],
> it doesn't check if partition is subscribed by checking TopicPartitionState
> cached is null or not, as done here by maybe
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
