Trying to setup consumer and producer in Kafka
up vote
0
down vote
favorite
I'm trying to make a simple producer-consumer flow over Kafka, using node-rdkafka
I'm using debug: 'all'
mode, this is what I get from the logs:
Producer: test [0]: MessageSet with 1 message(s) delivered
Consumer: Fetch topic test [0] at offset 38 (v2)
The fact that the consumer is changing offset when message is produced making me believe the connection with the broker is setup and authenticated correctly.
However, for some reason I don't get the message itself in the consumer.
This event is never called:
consumer.on('data', function(m) {
console.log("consumed", m)
});
I created a demo project for testing, you need to have a Kafka broker that supports SASL_SSL protocol in order to use it:
https://github.com/guysegal/kafka-example
Specifically, this is the consumer code:
https://github.com/guysegal/kafka-example/blob/master/src/consumer.ts
and the producer code:
https://github.com/guysegal/kafka-example/blob/master/src/producer.ts
javascript node.js apache-kafka kafka-consumer-api kafka-producer-api
add a comment |
up vote
0
down vote
favorite
I'm trying to make a simple producer-consumer flow over Kafka, using node-rdkafka
I'm using debug: 'all'
mode, this is what I get from the logs:
Producer: test [0]: MessageSet with 1 message(s) delivered
Consumer: Fetch topic test [0] at offset 38 (v2)
The fact that the consumer is changing offset when message is produced making me believe the connection with the broker is setup and authenticated correctly.
However, for some reason I don't get the message itself in the consumer.
This event is never called:
consumer.on('data', function(m) {
console.log("consumed", m)
});
I created a demo project for testing, you need to have a Kafka broker that supports SASL_SSL protocol in order to use it:
https://github.com/guysegal/kafka-example
Specifically, this is the consumer code:
https://github.com/guysegal/kafka-example/blob/master/src/consumer.ts
and the producer code:
https://github.com/guysegal/kafka-example/blob/master/src/producer.ts
javascript node.js apache-kafka kafka-consumer-api kafka-producer-api
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to make a simple producer-consumer flow over Kafka, using node-rdkafka
I'm using debug: 'all'
mode, this is what I get from the logs:
Producer: test [0]: MessageSet with 1 message(s) delivered
Consumer: Fetch topic test [0] at offset 38 (v2)
The fact that the consumer is changing offset when message is produced making me believe the connection with the broker is setup and authenticated correctly.
However, for some reason I don't get the message itself in the consumer.
This event is never called:
consumer.on('data', function(m) {
console.log("consumed", m)
});
I created a demo project for testing, you need to have a Kafka broker that supports SASL_SSL protocol in order to use it:
https://github.com/guysegal/kafka-example
Specifically, this is the consumer code:
https://github.com/guysegal/kafka-example/blob/master/src/consumer.ts
and the producer code:
https://github.com/guysegal/kafka-example/blob/master/src/producer.ts
javascript node.js apache-kafka kafka-consumer-api kafka-producer-api
I'm trying to make a simple producer-consumer flow over Kafka, using node-rdkafka
I'm using debug: 'all'
mode, this is what I get from the logs:
Producer: test [0]: MessageSet with 1 message(s) delivered
Consumer: Fetch topic test [0] at offset 38 (v2)
The fact that the consumer is changing offset when message is produced making me believe the connection with the broker is setup and authenticated correctly.
However, for some reason I don't get the message itself in the consumer.
This event is never called:
consumer.on('data', function(m) {
console.log("consumed", m)
});
I created a demo project for testing, you need to have a Kafka broker that supports SASL_SSL protocol in order to use it:
https://github.com/guysegal/kafka-example
Specifically, this is the consumer code:
https://github.com/guysegal/kafka-example/blob/master/src/consumer.ts
and the producer code:
https://github.com/guysegal/kafka-example/blob/master/src/producer.ts
javascript node.js apache-kafka kafka-consumer-api kafka-producer-api
javascript node.js apache-kafka kafka-consumer-api kafka-producer-api
edited Nov 20 at 15:03
cricket_007
78.1k1142108
78.1k1142108
asked Nov 20 at 6:27
Guy Segal
1901520
1901520
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
You may want to set the value 'auto.offset.reset': 'earliest'
and start the consumer again.
auto.offset.reset
This property decides the consumer starting position in case consumer starting with group which does not have last known state. For e.g. in case of new group-id id.
The reason for changing the value of auto.offset.reset
because if you produce first and starts consumer after that then topic offset has already increased and consumer will start with latest offset(increased offset) and reads the message from that point onward.
While in case of 'earliest'
consumer starts from first available message on topic.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You may want to set the value 'auto.offset.reset': 'earliest'
and start the consumer again.
auto.offset.reset
This property decides the consumer starting position in case consumer starting with group which does not have last known state. For e.g. in case of new group-id id.
The reason for changing the value of auto.offset.reset
because if you produce first and starts consumer after that then topic offset has already increased and consumer will start with latest offset(increased offset) and reads the message from that point onward.
While in case of 'earliest'
consumer starts from first available message on topic.
add a comment |
up vote
0
down vote
You may want to set the value 'auto.offset.reset': 'earliest'
and start the consumer again.
auto.offset.reset
This property decides the consumer starting position in case consumer starting with group which does not have last known state. For e.g. in case of new group-id id.
The reason for changing the value of auto.offset.reset
because if you produce first and starts consumer after that then topic offset has already increased and consumer will start with latest offset(increased offset) and reads the message from that point onward.
While in case of 'earliest'
consumer starts from first available message on topic.
add a comment |
up vote
0
down vote
up vote
0
down vote
You may want to set the value 'auto.offset.reset': 'earliest'
and start the consumer again.
auto.offset.reset
This property decides the consumer starting position in case consumer starting with group which does not have last known state. For e.g. in case of new group-id id.
The reason for changing the value of auto.offset.reset
because if you produce first and starts consumer after that then topic offset has already increased and consumer will start with latest offset(increased offset) and reads the message from that point onward.
While in case of 'earliest'
consumer starts from first available message on topic.
You may want to set the value 'auto.offset.reset': 'earliest'
and start the consumer again.
auto.offset.reset
This property decides the consumer starting position in case consumer starting with group which does not have last known state. For e.g. in case of new group-id id.
The reason for changing the value of auto.offset.reset
because if you produce first and starts consumer after that then topic offset has already increased and consumer will start with latest offset(increased offset) and reads the message from that point onward.
While in case of 'earliest'
consumer starts from first available message on topic.
edited Nov 20 at 10:33
answered Nov 20 at 10:23
bittu
324110
324110
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53387406%2ftrying-to-setup-consumer-and-producer-in-kafka%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown