# Timeout on executing kafka-topics

**URL:** <https://forum.confluent.io/t/timeout-on-executing-kafka-topics/37141>\
**Category:** Ops\
**Created:** [7 February 2025 08:55 UTC](https://forum.confluent.io/t/timeout-on-executing-kafka-topics/37141 "2025-02-07T08:55:09Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rand](https://avatars.discourse-cdn.com/v4/letter/r/ebca7d/32.png) [@Rand](https://forum.confluent.io/u/Rand)\
**Post date:** [7 February 2025 08:55 UTC](https://forum.confluent.io/t/timeout-on-executing-kafka-topics/37141/1 "2025-02-07T08:55:09Z")

</div>

Sorry for spamming threads, but those are all different topics (maybe with a similar root cause) and I thought it better to split those up so they can get tracked easier

Basically this thread is about getting a timeout when trying to run kafka-topics list (as a first test to see if connectivity is working).

```auto
 ./kafka-topics --bootstrap-server localhost:9094 --list
Error while executing topic command : Timed out waiting for a node assignment. Call: listTopics
[2025-02-07 08:48:39,707] ERROR org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment. Call: listTopics
 (org.apache.kafka.tools.TopicCommand)
[appuser@kafka-3 bin]$ ./kafka-topics --bootstrap-server localhost:9094 --version
7.8.0-ccs

```

Connectivity seems to be ok since the version command is fine, there is nothing in the logs (at loglevel Warn), but we do have issues with the cluster where we get a lot of timeouts for reasons we’re trying to identify…

---

<div class="post-metadata">

**Author:** ![mmuehlbeyer](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/mmuehlbeyer/32/1088_2.png) [@mmuehlbeyer](https://forum.confluent.io/u/mmuehlbeyer)\
**Post date:** [7 February 2025 14:34 UTC](https://forum.confluent.io/t/timeout-on-executing-kafka-topics/37141/2 "2025-02-07T14:34:13Z")

</div>

the version command does not connect to the cluster at all

you could try with:  
`kafka-topics --version`

probably the same as in your other one

> [@Metadata version problems on same host/docker image](https://forum.confluent.io/t/metadata-version-problems-on-same-host-docker-image/37137/1):
>
> Hi, as spin-off from my other topic I would like to trry to understand the metadata related errors we see. In the controller log on startup I find [2025-02-03 11:04:44,783] WARN [QuorumController id=3] Performing controller activation. The metadata log appears to be empty. Appending 1 bootstrap record(s) in metadata transaction at metadata.version 3.8-IV0 from bootstrap source ‘the binary bootstrap metadata file: /data/cpkafka-data/bootstrap.checkpoint’. Setting the ZK migration state to NON…

correct broker port chosen?

best,  
michael

---

<div class="post-metadata">

**Author:** ![Rand](https://avatars.discourse-cdn.com/v4/letter/r/ebca7d/32.png) [@Rand](https://forum.confluent.io/u/Rand)\
**Post date:** [7 February 2025 14:38 UTC](https://forum.confluent.io/t/timeout-on-executing-kafka-topics/37141/3 "2025-02-07T14:38:49Z")

</div>

Hi,  
yes these attempts connect to broker, I use the same Plaintext port 9094 here…

> ./kafka-topics --bootstrap-server server1:9094,server2:9094,server3:9094 --list  
> Error while executing topic command : Timed out waiting for a node assignment. Call: listTopics  
> [2025-02-07 14:47:21,504] ERROR org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment. Call: listTopics  
> (org.apache.kafka.tools.TopicCommand)

```
podman run -d --restart always \
    --name $KAFKA_INSTANCE \
    -h=server1 \
    -p 2281:2281 \
    -p 9093:9093 \
    -p 9094:9094 \
    -p 9095:9095 \
    -e KAFKA_NODE_ID=4 \
    -e KAFKA_PROCESS_ROLES='broker' \
    -e KAFKA_LISTENER_SECURITY_PROTOCOL_MAP='SSL:SSL,CONTROLLER:SSL,SSLINTERNAL:SSL, PLAIN:PLAINTEXT' \
    -e KAFKA_LISTENERS='SSLINTERNAL://:9093,SSL://:9095,PLAIN://:9094' \
    -e KAFKA_CONTROLLER_QUORUM_VOTERS='1@server1:9092,2@server2:9092,3@server3:9092' \
    -e KAFKA_INTER_BROKER_LISTENER_NAME='SSLINTERNAL' \
    -e KAFKA_SECURITY_PROTOCOL='SSL' \
    -e KAFKA_ADVERTISED_LISTENERS='SSLINTERNAL://server1:9093,SSL://:9095' \
    -e KAFKA_CONTROLLER_LISTENER_NAMES='CONTROLLER' \

```

---

<div class="post-metadata">

**Author:** ![dtroiano](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/dtroiano/32/1961_2.png) [@dtroiano](https://forum.confluent.io/u/dtroiano)\
**Post date:** [7 February 2025 16:24 UTC](https://forum.confluent.io/t/timeout-on-executing-kafka-topics/37141/4 "2025-02-07T16:24:23Z")

</div>

One issue is that port 9094 isn’t in `KAFKA_ADVERTISED_LISTENERS` – try adding `PLAIN://server1:9094`.

---

<div class="post-metadata">

**Author:** ![Rand](https://avatars.discourse-cdn.com/v4/letter/r/ebca7d/32.png) [@Rand](https://forum.confluent.io/u/Rand)\
**Post date:** [10 February 2025 06:17 UTC](https://forum.confluent.io/t/timeout-on-executing-kafka-topics/37141/5 "2025-02-10T06:17:13Z")

</div>

Man, I feel stupid now.  
That is so basic that even I could have seen that 😥

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/confluentcommunity/original/1X/c49438c90c9df282e9996fdf6971be890c71b65a.svg) [@system](https://forum.confluent.io/u/system)\
**Post date:** [17 February 2025 06:17 UTC](https://forum.confluent.io/t/timeout-on-executing-kafka-topics/37141/6 "2025-02-17T06:17:37Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.