简体   繁体   English

运行多个 kafka 独立 hdfs 连接器时出错

[英]Error running multiple kafka standalone hdfs connectors

We are trying to launch multiple standalone kafka hdfs connectors on a given node.我们正在尝试在给定节点上启动多个独立的kafka hdfs连接器。

For each connector, we are setting the rest.port and offset.storage.file.filename to different ports and path respectively.对于每个连接器,我们分别将rest.portoffset.storage.file.filename设置为不同的端口和路径。

Also kafka broker JMX port is @ 9999. kafka 代理 JMX 端口也是 @ 9999。

When I start the kafka standalone connector, I get the error当我启动 kafka 独立连接器时,出现错误

Error: Exception thrown by the agent: java.rmi.server.ExportException: Port already in use: 9999;错误:代理抛出的异常:java.rmi.server.ExportException:端口已在使用:9999; nested exception is: java.net.BindException: Address already in use (Bind failed)嵌套异常是:java.net.BindException:地址已在使用中(绑定失败)

Though the rest.port is set to 9100虽然 rest.port 设置为 9100

kafka version: 2.12-0.10.2.1卡夫卡版本:2.12-0.10.2.1

kafka-connect-hdfs version: 3.2.1 kafka-connect-hdfs 版本:3.2.1

Please help.请帮忙。

We are trying to launch multiple standalone kafka hdfs connectors on a given node. 我们正在尝试在给定节点上启动多个独立的kafka hdfs连接器。

Have you considered running these multiple connectors within a single instance of Kafka Connect? 您是否考虑过在单个Kafka Connect实例中运行这些多个连接器? This might make things easier. 这可能使事情变得容易。

Kafka Connect itself can handle running multiple connectors within a single worker process. Kafka Connect本身可以处理在单个工作进程中运行多个连接器的情况。 Kafka Connect in distributed mode can run on a single node, or across multiple ones. 分布式模式下的Kafka Connect可以在单个节点上运行,也可以在多个节点上运行。

For those who trying to use rest.port flag and still getting Address already in use error.对于那些尝试使用rest.port标志但仍然收到Address already in use错误的人。 That flag has been marked as deprecated in KIP-208 and finally removed in PR .该标志已在KIP-208中标记为已弃用,并最终在PR中删除。
From that point listeners can be used to change default REST port.从那时起, listeners器可用于更改默认的 REST 端口。
Examples from Javadoc来自 Javadoc 的例子

listeners=HTTP://myhost:8083
listeners=HTTP://:8083

Configuring and Running Workers - Standalone mode 配置和运行 Worker - 独立模式

You may have open Kafka Connect connections that you don't know about. 您可能会打开未知的Kafka Connect连接。 You can check this with: 您可以使用以下方法进行检查:

ps -ef | grep connect

If you find any, kill those processes. 如果发现任何问题,请终止这些进程。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Kafka Connect:多个独立连接器可以写入同一个 HDFS 目录吗? - Kafka Connect: can multiple standalone connectors write to the same HDFS directory? Kafka 连接器 - 独立模式 - Kafka connectors - Standalone mode 具有多个连接器和一个主题的分布式Kafka Connect - Distributed Kafka Connect with multiple Connectors and one Topic Kafka 2.0 - KafkaConnect 连接器中的多个 Kerberos 主体 - Kafka 2.0 - Multiple Kerberos Principals in KafkaConnect Connectors 错误 500 向多个代理注册 kafka 连接 PG 连接器时无法创建 PG 连接 - Error 500 Could not create PG connection when registering kafka connect PG connectors with multiple brokers 卡夫卡中针对不同主题的多个连接器将到达同一节点 - multiple connectors in kafka to different topics are going to same node 在Kafka中启动多个连接器通过单个分布式工作者连接吗? - Starting multiple connectors in Kafka Connect withing single distributed worker? Confluent Kafka Connect:以同步方式运行多个接收器连接器 - Confluent Kafka Connect : Run multiple sink connectors in synchronous way 如何为单个主题设置多个Kafka JDBC接收器连接器 - How to setup multiple Kafka JDBC sink connectors for a single topic 在 Kafka Connect 分布式模式下为多个主题配置连接器 - Configuring connectors for multiple topics on Kafka Connect Distributed Mode
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM