阿帕奇卡夫卡2.3+;Node.js 10.15+;消费者+;制作人
我正在尝试使用nodejs从远程机器连接到远程apachekafka服务器。我无法从nodejs代码生成有关所需卡夫卡主题的消息。我也无法使用该主题中的任何数据 我正在使用ApacheKafka版本2.12\u2.2.1以及Java 8。我还使用了节点版本8.11.0。我启动了zookeeper服务器和kafka服务器。我在ubuntu机器上本地创建了一个主题和一个生产者和消费者来检查ApacheKafka的工作情况,并且我能够生成和消费关于主题的消息。当我使用nodejs在远程windows机器上尝试同样的方法时,我无法得到任何结果。我还尝试将我的服务器添加到config/server.properties文件中的侦听器和播发的.listeners中,但仍然无法工作 我的问题: 我想从节点js建立到kafka服务器的远程连接,并使用主题下生成的消息。 任何帮助都将不胜感激:)谢谢 以下是生产商代码:阿帕奇卡夫卡2.3+;Node.js 10.15+;消费者+;制作人,node.js,apache-kafka,kafka-consumer-api,kafka-producer-api,Node.js,Apache Kafka,Kafka Consumer Api,Kafka Producer Api,我正在尝试使用nodejs从远程机器连接到远程apachekafka服务器。我无法从nodejs代码生成有关所需卡夫卡主题的消息。我也无法使用该主题中的任何数据 我正在使用ApacheKafka版本2.12\u2.2.1以及Java 8。我还使用了节点版本8.11.0。我启动了zookeeper服务器和kafka服务器。我在ubuntu机器上本地创建了一个主题和一个生产者和消费者来检查ApacheKafka的工作情况,并且我能够生成和消费关于主题的消息。当我使用nodejs在远程windows机
var kafka = require('kafka-node'),
Producer = kafka.Producer,
KeyedMessage = kafka.KeyedMessage,
client = new kafka.KafkaClient({kafkaHost: '192.168.1.104:9092'}),
producer = new Producer(client),
payloads = [
{ topic: 'topic1', messages: 'hi', partition: 2 }
];
producer.on('ready', function () {
console.log('Connected');
setInterval(() => {
producer.send(payloads, function (err, data) {
console.log(data);
});
}, 1000);
});
producer.on('error', function (err) {console.error('Error occurred:', err);})
C:\Users\user\Documents\nodejs>node kafka-producer.js
Connected
undefined
以下是消费者代码:
var kafka = require('kafka-node'),
Consumer = kafka.Consumer,
client = new kafka.KafkaClient({kafkaHost: '192.168.1.104:9092'}),
consumer = new Consumer(client,
[{ topic: 'topic1', offset: 0}],
{
autoCommit: false
}
);
consumer.on('message', function (message) {
console.log(message);
});
consumer.on('error', function (err) {
console.log('Error:',err);
})
consumer.on('offsetOutOfRange', function (err) {
console.log('offsetOutOfRange:',err);
})
Error: { TimeoutError: Request timed out after 30000ms at new TimeoutError (C:\Users\user\Documents\nodejs\node_modules\kafka-node\lib\errors\TimeoutError.js:6:9)
at Timeout.setTimeout [as _onTimeout] (C:\Users\user\Documents\nodejs\node_modules\kafka-node\lib\kafkaClient.js:491:14)
at ontimeout (timers.js:482:11)
at tryOnTimeout (timers.js:317:5)
at Timer.listOnTimeout (timers.js:277:5) message:
'Request timed out after 30000ms' }
列出了节点js终端的响应消息
对于生产者代码:
var kafka = require('kafka-node'),
Producer = kafka.Producer,
KeyedMessage = kafka.KeyedMessage,
client = new kafka.KafkaClient({kafkaHost: '192.168.1.104:9092'}),
producer = new Producer(client),
payloads = [
{ topic: 'topic1', messages: 'hi', partition: 2 }
];
producer.on('ready', function () {
console.log('Connected');
setInterval(() => {
producer.send(payloads, function (err, data) {
console.log(data);
});
}, 1000);
});
producer.on('error', function (err) {console.error('Error occurred:', err);})
C:\Users\user\Documents\nodejs>node kafka-producer.js
Connected
undefined
消费者代码:
var kafka = require('kafka-node'),
Consumer = kafka.Consumer,
client = new kafka.KafkaClient({kafkaHost: '192.168.1.104:9092'}),
consumer = new Consumer(client,
[{ topic: 'topic1', offset: 0}],
{
autoCommit: false
}
);
consumer.on('message', function (message) {
console.log(message);
});
consumer.on('error', function (err) {
console.log('Error:',err);
})
consumer.on('offsetOutOfRange', function (err) {
console.log('offsetOutOfRange:',err);
})
Error: { TimeoutError: Request timed out after 30000ms at new TimeoutError (C:\Users\user\Documents\nodejs\node_modules\kafka-node\lib\errors\TimeoutError.js:6:9)
at Timeout.setTimeout [as _onTimeout] (C:\Users\user\Documents\nodejs\node_modules\kafka-node\lib\kafkaClient.js:491:14)
at ontimeout (timers.js:482:11)
at tryOnTimeout (timers.js:317:5)
at Timer.listOnTimeout (timers.js:277:5) message:
'Request timed out after 30000ms' }
我已将server.properties文件附加到下面:
Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# see kafka.server.KafkaConfig for additional details and defaults
############################# Server Basics #############################
# The id of the broker. This must be set to a unique integer for each broker.
broker.id=0
############################# Socket Server Settings #############################
# The address the socket server listens on. It will get the value returned from
# java.net.InetAddress.getCanonicalHostName() if not configured.
# FORMAT:
# listeners = listener_name://host_name:port
# EXAMPLE:
# listeners = PLAINTEXT://your.host.name:9092
#listeners=PLAINTEXT://localhost:9092
#listeners=PLAINTEXT://192.168.1.88:9092
# Hostname and port the broker will advertise to producers and consumers. If not set,
# it uses the value for "listeners" if configured. Otherwise, it will use the value
# returned from java.net.InetAddress.getCanonicalHostName().
advertised.listeners=PLAINTEXT://192.168.1.88:9092,
advertised.listeners=PLAINTEXT://localhost:9092
# Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details
#listener.security.protocol.map=PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL
# The number of threads that the server uses for receiving requests from the network and sending responses to the network
num.network.threads=3
# The number of threads that the server uses for processing requests, which may include disk I/O
num.io.threads=8
# The send buffer (SO_SNDBUF) used by the socket server
socket.send.buffer.bytes=102400
# The receive buffer (SO_RCVBUF) used by the socket server
socket.receive.buffer.bytes=102400
# The maximum size of a request that the socket server will accept (protection against OOM)
socket.request.max.bytes=104857600
############################# Log Basics #############################
# A comma separated list of directories under which to store log files
log.dirs=/tmp/kafka-logs
# The default number of log partitions per topic. More partitions allow greater
# parallelism for consumption, but this will also result in more files across
# the brokers.
num.partitions=1
# The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.
# This value is recommended to be increased for installations with data dirs located in RAID array.
num.recovery.threads.per.data.dir=1
############################# Internal Topic Settings #############################
# The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state"
# For anything other than development testing, a value greater than 1 is recommended for to ensure availability such as 3.
offsets.topic.replication.factor=1
transaction.state.log.replication.factor=1
transaction.state.log.min.isr=1
############################# Log Flush Policy #############################
# Messages are immediately written to the filesystem but by default we only fsync() to sync
# the OS cache lazily. The following configurations control the flush of data to disk.
# There are a few important trade-offs here:
# 1. Durability: Unflushed data may be lost if you are not using replication.
# 2. Latency: Very large flush intervals may lead to latency spikes when the flush does occur as there will be a lot of data to flush.
# 3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to excessive seeks.
# The settings below allow one to configure the flush policy to flush data after a period of time or
# every N messages (or both). This can be done globally and overridden on a per-topic basis.
# The number of messages to accept before forcing a flush of data to disk
#log.flush.interval.messages=10000
# The maximum amount of time a message can sit in a log before we force a flush
#log.flush.interval.ms=1000
############################# Log Retention Policy #############################
# The following configurations control the disposal of log segments. The policy can
# be set to delete segments after a period of time, or after a given size has accumulated.
# A segment will be deleted whenever *either* of these criteria are met. Deletion always happens
# from the end of the log.
# The minimum age of a log file to be eligible for deletion due to age
log.retention.hours=168
# A size-based retention policy for logs. Segments are pruned from the log unless the remaining
# segments drop below log.retention.bytes. Functions independently of log.retention.hours.
#log.retention.bytes=1073741824
# The maximum size of a log segment file. When this size is reached a new log segment will be created.
log.segment.bytes=1073741824
# The interval at which log segments are checked to see if they can be deleted according
# to the retention policies
log.retention.check.interval.ms=300000
############################# Zookeeper #############################
# Zookeeper connection string (see zookeeper docs for details).
# This is a comma separated host:port pairs, each corresponding to a zk
# server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002".
# You can also append an optional chroot string to the urls to specify the
# root directory for all kafka znodes.
zookeeper.connect=localhost:2181
# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=6000
############################# Group Coordinator Settings #############################
# The following configuration specifies the time, in milliseconds, that the GroupCoordinator will delay the initial consumer rebalance.
# The rebalance will be further delayed by the value of group.initial.rebalance.delay.ms as new members join the group, up to a maximum of max.poll.interval.ms.
# The default value for this is 3 seconds.
# We override this to 0 here as it makes for a better out-of-the-box experience for development and testing.
# However, in production environments the default value of 3 seconds is more suitable as this will help to avoid unnecessary, and potentially expensive, rebalances dur$
group.initial.rebalance.delay.ms=0
我能够通过使用以下代码解决这个问题。我目前已经设置了代码来生成增量数字,以测试消费者是否工作正常 节点js中的生产者代码:
const kafka = require('kafka-node');
const kafka_topic = 'sample';
try {
const Producer = kafka.Producer;
const client = new kafka.KafkaClient({kafkaHost: '192.168.1.246:9092'});
const producer = new Producer(client);
console.log("Producer Initialised..");
producer.on('ready', function() {
let num = 0;
setInterval(() => {
let payloads = [
{
topic: 'sample',
messages: num
}
];
producer.send(payloads, (err, data) => {
if (err) {
console.log('[kafka-producer -> '+kafka_topic+']: broker update failed');
} else {
console.log('[kafka-producer -> '+kafka_topic+']: broker update success');
}
});
num++;
}, 2000);
});
producer.on('error', function(err) {
console.log(err);
console.log('[kafka-producer -> '+kafka_topic+']: connection errored');
throw err;
});
}
catch(e) {
console.log(e);
}
let kafka =require("kafka-node");
const client = new kafka.KafkaClient({kafkaHost: '192.168.1.246:9092'});
console.log("Initialised..");
const topics = [{
topic: 'sample',
offset: 0, //default 0
partition: 0 // default 0
}];
const options = {
autoCommit: true
};
const consumer = new kafka.Consumer(client, topics, options);
consumer.setMaxListeners(11);
consumer.on("ready", function(message) {
console.log("I am ready");
});
consumer.on("message", function(message) {
console.log("Hey got message");
// console.log(message);
console.log("Message: ", message.value);
});
consumer.on("error", function(err) {
console.log("error", err);
});
消费者代码是节点js:
const kafka = require('kafka-node');
const kafka_topic = 'sample';
try {
const Producer = kafka.Producer;
const client = new kafka.KafkaClient({kafkaHost: '192.168.1.246:9092'});
const producer = new Producer(client);
console.log("Producer Initialised..");
producer.on('ready', function() {
let num = 0;
setInterval(() => {
let payloads = [
{
topic: 'sample',
messages: num
}
];
producer.send(payloads, (err, data) => {
if (err) {
console.log('[kafka-producer -> '+kafka_topic+']: broker update failed');
} else {
console.log('[kafka-producer -> '+kafka_topic+']: broker update success');
}
});
num++;
}, 2000);
});
producer.on('error', function(err) {
console.log(err);
console.log('[kafka-producer -> '+kafka_topic+']: connection errored');
throw err;
});
}
catch(e) {
console.log(e);
}
let kafka =require("kafka-node");
const client = new kafka.KafkaClient({kafkaHost: '192.168.1.246:9092'});
console.log("Initialised..");
const topics = [{
topic: 'sample',
offset: 0, //default 0
partition: 0 // default 0
}];
const options = {
autoCommit: true
};
const consumer = new kafka.Consumer(client, topics, options);
consumer.setMaxListeners(11);
consumer.on("ready", function(message) {
console.log("I am ready");
});
consumer.on("message", function(message) {
console.log("Hey got message");
// console.log(message);
console.log("Message: ", message.value);
});
consumer.on("error", function(err) {
console.log("error", err);
});
对kafka文件夹中的config/server.properties文件进行以下更改。
注意:-添加您正在使用的安装了kafka和zookeeper的当前计算机的IP地址,以便通过网络从远程计算机使用kafka
Server.properties file
Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# see kafka.server.KafkaConfig for additional details and defaults
############################# Server Basics #############################
# The id of the broker. This must be set to a unique integer for each broker.
broker.id=0
############################# Socket Server Settings #############################
# The address the socket server listens on. It will get the value returned from
# java.net.InetAddress.getCanonicalHostName() if not configured.
# FORMAT:
# listeners = listener_name://host_name:port
# EXAMPLE:
# listeners = PLAINTEXT://your.host.name:9092
#listeners=PLAINTEXT://localhost:9092
listeners=PLAINTEXT://192.168.1.246:9092
# Hostname and port the broker will advertise to producers and consumers. If not set,
# it uses the value for "listeners" if configured. Otherwise, it will use the value
# returned from java.net.InetAddress.getCanonicalHostName().
#advertised.listeners=PLAINTEXT://localhost:9092,
# Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details
#listener.security.protocol.map=PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL
# The number of threads that the server uses for receiving requests from the network and sending responses to the network
num.network.threads=3
# The number of threads that the server uses for processing requests, which may include disk I/O
num.io.threads=8
# The send buffer (SO_SNDBUF) used by the socket server
socket.send.buffer.bytes=102400
# The receive buffer (SO_RCVBUF) used by the socket server
socket.receive.buffer.bytes=102400
# The maximum size of a request that the socket server will accept (protection against OOM)
socket.request.max.bytes=104857600
############################# Log Basics #############################
# A comma separated list of directories under which to store log files
log.dirs=/tmp/kafka-logs
# The default number of log partitions per topic. More partitions allow greater
# parallelism for consumption, but this will also result in more files across
# the brokers.
num.partitions=1
# The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.
# This value is recommended to be increased for installations with data dirs located in RAID array.
num.recovery.threads.per.data.dir=1
############################# Internal Topic Settings #############################
# The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state"
# For anything other than development testing, a value greater than 1 is recommended for to ensure availability such as 3.
offsets.topic.replication.factor=1
transaction.state.log.replication.factor=1
transaction.state.log.min.isr=1
############################# Log Flush Policy #############################
# Messages are immediately written to the filesystem but by default we only fsync() to sync
# the OS cache lazily. The following configurations control the flush of data to disk.
# There are a few important trade-offs here:
# 1. Durability: Unflushed data may be lost if you are not using replication.
# 2. Latency: Very large flush intervals may lead to latency spikes when the flush does occur as there will be a lot of data to flush.
# 3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to excessive seeks.
# The settings below allow one to configure the flush policy to flush data after a period of time or
# every N messages (or both). This can be done globally and overridden on a per-topic basis.
# The number of messages to accept before forcing a flush of data to disk
#log.flush.interval.messages=10000
# The maximum amount of time a message can sit in a log before we force a flush
#log.flush.interval.ms=1000
############################# Log Retention Policy #############################
# The following configurations control the disposal of log segments. The policy can
# be set to delete segments after a period of time, or after a given size has accumulated.
# A segment will be deleted whenever *either* of these criteria are met. Deletion always happens
# from the end of the log.
# The minimum age of a log file to be eligible for deletion due to age
log.retention.hours=168
# A size-based retention policy for logs. Segments are pruned from the log unless the remaining
# segments drop below log.retention.bytes. Functions independently of log.retention.hours.
#log.retention.bytes=1073741824
# The maximum size of a log segment file. When this size is reached a new log segment will be created.
log.segment.bytes=1073741824
# The interval at which log segments are checked to see if they can be deleted according
# to the retention policies
log.retention.check.interval.ms=300000
############################# Zookeeper #############################
# Zookeeper connection string (see zookeeper docs for details).
# This is a comma separated host:port pairs, each corresponding to a zk
# server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002".
# You can also append an optional chroot string to the urls to specify the
# root directory for all kafka znodes.
zookeeper.connect=localhost:2181
# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=6000
############################# Group Coordinator Settings #############################
# The following configuration specifies the time, in milliseconds, that the GroupCoordinator will delay the initial consumer rebalance.
# The rebalance will be further delayed by the value of group.initial.rebalance.delay.ms as new members join the group, up to a maximum of max.poll.interval.ms.
# The default value for this is 3 seconds.
# We override this to 0 here as it makes for a better out-of-the-box experience for development and testing.
# However, in production environments the default value of 3 seconds is more suitable as this will help to avoid unnecessary, and potentially expensive, rebalances dur$
group.initial.rebalance.delay.ms=0
这在远程机器上也能完美运行,并已在node版本10.15.0和8.11.0以及Kafka当前LTS版本2.3.0和Zookeeper版本3.5.5
希望这有帮助:)请共享服务器。属性file@cricket_007我已附加server.properties文件。谢谢为什么你有多行听众和广告听众?注意:两个
侦听器
行都有注释,因此实际上不做任何事情,但是应该是纯文本://0.0.0.0:9092@cricket_007我尝试将其更改为纯文本://0.0.0.0:9092,但由于致命异常(Kafka.Kafka$)退出Kafka时出现以下错误错误java.lang.IllegalArgumentException:要求失败:播发。侦听器无法使用不可路由的元地址0.0.0.0。使用可路由的IP地址。
@cricket\u 007我曾尝试将侦听器更改为该地址,但它给了我相同的错误。不过,我还是找到了一些其他的代码,这些代码很有魅力。感谢您的帮助:)如果您希望卡夫卡数据持久化,请不要将其存储在/tmp
@cricket\u 007中。非常感谢@BhaskarSen:感谢您帮助社区提供如此详细的答案。