NO Broker Available error in node-red version 3.1.10 V

General
1

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

{
  "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!

2

Hi welcome to the forum.

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

You should check the nodes issue tracker - 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.

3

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