# NO Broker Available error in node-red version 3.1.10 V

**URL:** https://discourse.nodered.org/t/no-broker-available-error-in-node-red-version-3-1-10-v/95022
**Category:** General
**Created:** [31 January 2025 07:55 UTC](https://discourse.nodered.org/t/no-broker-available-error-in-node-red-version-3-1-10-v/95022 "2025-01-31T07:55:16Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![gautamt572](https://avatars.discourse-cdn.com/v4/letter/g/898d66/32.png) [@gautamt572](https://discourse.nodered.org/u/gautamt572)
#### Post date: [31 January 2025 07:55 UTC](https://discourse.nodered.org/t/no-broker-available-error-in-node-red-version-3-1-10-v/95022/1 "2025-01-31T07:55:16Z")

</div>

We are getting below error in sometime in node-red flows because of this data flow is impacting ,could you please help why this error occurs in node red frequecntly.

`[error] Kafka Broker`

```auto
{
  "label": "Metadata refresh ",
  "error": "Broker not available (loadMetadataForTopics)",
  "stack": "BrokerNotAvailableError: Broker not available (loadMetadataForTopics)
    at new BrokerNotAvailableError (/usr/src/node-red/node_modules/kafka-node/lib/errors/BrokerNotAvailableError.js:11:9)
    at KafkaClient.loadMetadataForTopics (/usr/src/node-red/node_modules/kafka-node/lib/kafkaClient.js:891:21)
    at Admin.listTopics (/usr/src/node-red/node_modules/kafka-node/lib/admin.js:44:15)
    at KafkaBrokerNode.adminRequestSend (/usr/src/node-red/node_modules/node-red-contrib-kafka-manager/kafkaManager/kafkaBroker.js:15:39)
    at KafkaBrokerNode.adminRequest (/usr/src/node-red/node_modules/node-red-contrib-kafka-manager/kafkaManager/kafkaBroker.js:32:8)
    at Metadata.refreshFunction (/usr/src/node-red/node_modules/node-red-contrib-kafka-manager/kafkaManager/Metadata.js:45:14)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7)"
}

```

Admin edit: readability, use a code block!

---

<div class="post-metadata">

### Author: ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [31 January 2025 08:53 UTC](https://discourse.nodered.org/t/no-broker-available-error-in-node-red-version-3-1-10-v/95022/2 "2025-01-31T08:53:36Z")

</div>

Hi welcome to the forum.

the last line in the stack trace reveals the node type causing an issue:

> [@gautamt572](#):
>
> ```auto
> at Metadata.refreshFunction (/usr/src/node-red/node_modules/node-red-contrib-kafka-manager/kafkaManager/Metadata.js:45:14)
> 
> ```

You should check the nodes [issue tracker](https://github.com/peterprib/node-red-contrib-kafka-manager/issues?q=is%3Aissue%20) - there may be a known fix. If not, you can raise an issue in the hope the author fixes it. Alternatively, try using an alternative kafka node.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [1 April 2025 08:54 UTC](https://discourse.nodered.org/t/no-broker-available-error-in-node-red-version-3-1-10-v/95022/3 "2025-04-01T08:54:18Z")

</div>

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