[
https://issues.apache.org/jira/browse/KAFKA-16766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk True updated KAFKA-16766:
------------------------------
Component/s: clients
> New consumer offsetsForTimes timeout exception does not have the proper
> message
> -------------------------------------------------------------------------------
>
> Key: KAFKA-16766
> URL: https://issues.apache.org/jira/browse/KAFKA-16766
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Affects Versions: 3.7.0
> Reporter: Lianet Magrans
> Priority: Major
> Labels: kip-848-client-support
> Fix For: 3.8.0
>
>
> If a call to consumer.offsetsForTimes times out, the new AsyncKafkaConsumer
> will throw a org.apache.kafka.common.errors.TimeoutException as expected, but
> with the following as message: "java.util.concurrent.TimeoutException".
> We should provide a clearer message, and I would even say we keep the same
> message that the LegacyConsumer shows in this case, ex: "Failed to get
> offsets by times in 60000ms".
> To fix this we should consider catching the timeout exception in the consumer
> when offsetsForTimes result times out
> ([here|https://github.com/apache/kafka/blob/0e023e1f736ea03568032cc282803df8e61eb451/clients/src/main/java/org/apache/kafka/clients/consumer/internals/AsyncKafkaConsumer.java#L1115]),
> and propagate it with the message specific to offsetsForTimes.
> Same situation exists for beginningOffsets and endOffsets. All 3 funcs show
> the same timeout message in the LegacyConsumer (defined
> [here|https://github.com/apache/kafka/blob/0e023e1f736ea03568032cc282803df8e61eb451/clients/src/main/java/org/apache/kafka/clients/consumer/internals/OffsetFetcher.java#L182]),
> but do not have a clear message in the Async, so we should fix them all 3.
> With the fix, we should write tests for each func, like the ones defined for
> the Legacy Consumer
> ([here|https://github.com/apache/kafka/blob/0e023e1f736ea03568032cc282803df8e61eb451/clients/src/test/java/org/apache/kafka/clients/consumer/KafkaConsumerTest.java#L3244-L3276]).
> Note that we would need different tests, added to AsyncKafkaConsumerTest,
> given that the async consumer issues a FindCoordinator request in this case,
> but the AsyncConsumer does, so it does not account for that when matching
> requests/responses in the current tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
