[
https://issues.apache.org/jira/browse/KAFKA-19500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Schofield resolved KAFKA-19500.
--------------------------------------
Fix Version/s: 4.2.0
Resolution: Fixed
> kafka-consumer-groups.sh should fail quickly if the partition leader is
> unavailable
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-19500
> URL: https://issues.apache.org/jira/browse/KAFKA-19500
> Project: Kafka
> Issue Type: Improvement
> Reporter: Chia-Ping Tsai
> Assignee: kangning.li
> Priority: Minor
> Fix For: 4.2.0
>
>
> {code:java}
> Error: Executing consumer group command failed due to
> java.util.concurrent.ExecutionException:
> org.apache.kafka.common.errors.TimeoutException:
> Call(callName=listOffsets(api=METADATA), deadlineMs=1752487911886,
> tries=492805, nextAllowedTryMs=1752487912888) timed out at 1752487911888
> after 492805 attempt(s)
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> org.apache.kafka.common.errors.TimeoutException:
> Call(callName=listOffsets(api=METADATA), deadlineMs=1752487911886,
> tries=492805, nextAllowedTryMs=1752487912888) timed out at 1752487911888
> after 492805 attempt(s)
> at
> org.apache.kafka.tools.OffsetsUtils.getLogTimestampOffsets(OffsetsUtils.java:190)
> at
> org.apache.kafka.tools.OffsetsUtils.resetByDuration(OffsetsUtils.java:352)
> at
> org.apache.kafka.tools.consumer.group.ConsumerGroupCommand$ConsumerGroupService.prepareOffsetsToReset(ConsumerGroupCommand.java:1015)
> at
> org.apache.kafka.tools.consumer.group.ConsumerGroupCommand$ConsumerGroupService.resetOffsetsForInactiveGroup(ConsumerGroupCommand.java:704)
> at
> org.apache.kafka.tools.consumer.group.ConsumerGroupCommand$ConsumerGroupService.lambda$resetOffsets$24(ConsumerGroupCommand.java:681)
> at java.base/java.util.HashMap.forEach(HashMap.java:1429)
> at
> org.apache.kafka.tools.consumer.group.ConsumerGroupCommand$ConsumerGroupService.resetOffsets(ConsumerGroupCommand.java:675)
> at
> org.apache.kafka.tools.consumer.group.ConsumerGroupCommand.run(ConsumerGroupCommand.java:130)
> at
> org.apache.kafka.tools.consumer.group.ConsumerGroupCommand.main(ConsumerGroupCommand.java:110)
> Caused by: java.util.concurrent.ExecutionException:
> org.apache.kafka.common.errors.TimeoutException:
> Call(callName=listOffsets(api=METADATA), deadlineMs=1752487911886,
> tries=492805, nextAllowedTryMs=1752487912888) timed out at 1752487911888
> after 492805 attempt(s)
> at
> java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396)
> at
> java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073)
> at
> org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:155)
> at
> org.apache.kafka.tools.OffsetsUtils.getLogTimestampOffsets(OffsetsUtils.java:167)
> ... 8 more
> {code}
> `Admin#listOffsets` needs to communicate to the partition leader to get
> latest information. Hence, the call hangs if the node hosting the leader is
> unavailable. It should fail quickly by using `describeTopics` to check the
> leaders for all input partitions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
