[
https://issues.apache.org/jira/browse/KAFKA-9220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138112#comment-17138112
]
sats commented on KAFKA-9220:
-----------------------------
Yes for 'bin/kafka-leader-election.sh' this can be taken as a bug, but for
earlier version 'kafka-preferred-replica-election.sh' it don't have
`-–admin.config` it just take two params '--zookeeper' and '--path-to-json-file
topicPartitionList.json' i think it need KIP.
> TimeoutException when using kafka-preferred-replica-election
> ------------------------------------------------------------
>
> Key: KAFKA-9220
> URL: https://issues.apache.org/jira/browse/KAFKA-9220
> Project: Kafka
> Issue Type: Bug
> Components: admin
> Affects Versions: 2.3.0
> Reporter: Or Shemesh
> Priority: Major
>
> When running kafka-preferred-replica-election --bootstrap-server xxx:9092
> I'm getting this error:
> Timeout waiting for election resultsTimeout waiting for election
> resultsException in thread "main" kafka.common.AdminCommandFailedException at
> kafka.admin.PreferredReplicaLeaderElectionCommand$AdminClientCommand.electPreferredLeaders(PreferredReplicaLeaderElectionCommand.scala:246)
> at
> kafka.admin.PreferredReplicaLeaderElectionCommand$.run(PreferredReplicaLeaderElectionCommand.scala:78)
> at
> kafka.admin.PreferredReplicaLeaderElectionCommand$.main(PreferredReplicaLeaderElectionCommand.scala:42)
> at
> kafka.admin.PreferredReplicaLeaderElectionCommand.main(PreferredReplicaLeaderElectionCommand.scala)Caused
> by: org.apache.kafka.common.errors.TimeoutException: Aborted due to timeout.
>
> Because we have a big cluster and getting all the data from the zookeeper is
> taking more the 30 second.
>
> After searching the code I saw that the 30 second is hard-coded can you
> enable us to set the timeout as parameter?
> [https://github.com/confluentinc/kafka/blob/master/core/src/main/scala/kafka/admin/PreferredReplicaLeaderElectionCommand.scala]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
