# Error: Topic XXXX not present in metadata after 60000 ms

**URL:** <https://forum.confluent.io/t/error-topic-xxxx-not-present-in-metadata-after-60000-ms/2618>\
**Category:** Clients\
**Created:** [31 August 2021 19:12 UTC](https://forum.confluent.io/t/error-topic-xxxx-not-present-in-metadata-after-60000-ms/2618 "2021-08-31T19:12:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![fostrit](https://avatars.discourse-cdn.com/v4/letter/f/3be4f8/32.png) [@fostrit](https://forum.confluent.io/u/fostrit)\
**Post date:** [31 August 2021 19:12 UTC](https://forum.confluent.io/t/error-topic-xxxx-not-present-in-metadata-after-60000-ms/2618/1 "2021-08-31T19:12:58Z")

</div>

hello everyone, am having a problem that occurs randomly at the time when a producer tries to generate messages to any topic, this is the error that the producer receives and I do not see errors in Kafka’s logs:

Error: Topic XXXX not present in metadata after 60000 ms

This can be given in any topic and at any time, there is no time pattern and the connection to kafka is stable, also the configuration in kafka to automatically create a topic is enabled auto.create.topics.enable: “true”

I leave the configuration of the producer that is being used to create messages:

retries=2700000  
retry.backoff.ms=1000  
batch.size=131072  
buffer.memory=66554432  
bootstrap.servers=Ipserver:9094  
compression.type=snappy  
acks=all  
linger.ms=100  
request.timeout.ms=60000  
enable.idempotence=true  
delivery.timeout.ms=180300  
metadata.max.idle.ms=180000

I have a cluster of 3 nodes in azure AKS

can it be some setting in the Producer parameters that can be added or changed to test if the behavior changes?

in a blog I saw that they added these parameters but I don’t know if it would be good to apply them

`{ "key": "connections.max.idle.ms", "value": "60000" }, { "key": "metadata.max.idle.ms", "value": "60000" }, { "key": "metadata.max.age.ms", "value": "60000" }`

---

<div class="post-metadata">

**Author:** ![mfor777](https://avatars.discourse-cdn.com/v4/letter/m/9de053/32.png) [@mfor777](https://forum.confluent.io/u/mfor777)\
**Post date:** [27 July 2022 12:23 UTC](https://forum.confluent.io/t/error-topic-xxxx-not-present-in-metadata-after-60000-ms/2618/2 "2022-07-27T12:23:03Z")

</div>

Hi @fostrit  
Did you ever resolve this? I have encountered the same issue  
Thanks

---

<div class="post-metadata">

**Author:** ![dolly](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/dolly/32/2635_2.png) [@dolly](https://forum.confluent.io/u/dolly)\
**Post date:** [26 December 2022 08:37 UTC](https://forum.confluent.io/t/error-topic-xxxx-not-present-in-metadata-after-60000-ms/2618/3 "2022-12-26T08:37:58Z")

</div>

Hi @mfor777 @fostrit  
Please suggest how were you able to resolve this issue. I am also facing the same thing.  
Thanks

---

<div class="post-metadata">

**Author:** ![fostrit](https://avatars.discourse-cdn.com/v4/letter/f/3be4f8/32.png) [@fostrit](https://forum.confluent.io/u/fostrit)\
**Post date:** [27 December 2022 03:03 UTC](https://forum.confluent.io/t/error-topic-xxxx-not-present-in-metadata-after-60000-ms/2618/4 "2022-12-27T03:03:12Z")

</div>

Hi @dolly and @mfor777, I was able to solve the problem by adding some settings in kafkaproducer.properties, you can see this in the following github ticket of the strimzi kafka project which I also opened [Error: Topic XXXX not present in metadata after 60000 ms · Discussion #5498 · strimzi/strimzi-kafka-operator · GitHub](https://github.com/strimzi/strimzi-kafka-operator/discussions/5498#discussioncomment-2706418)

---

<div class="post-metadata">

**Author:** ![Joe](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/joe/32/156_2.png) [@Joe](https://forum.confluent.io/u/Joe)\
**Post date:** [10 February 2025 19:55 UTC](https://forum.confluent.io/t/error-topic-xxxx-not-present-in-metadata-after-60000-ms/2618/5 "2025-02-10T19:55:59Z")

</div>