consumer receives no message from Kafka
up vote
1
down vote
favorite
I am using docker-compose.yml to set up multi-layer web app.
batch:
image: tp33/django
container_name: batch
links:
- kafka:kafka
- es:es
depends_on:
- kafka
- es
volumes:
- ./batch_layer:/app
networks:
- mynet
command: bash -c "cd /app && python consumer.py"
kafka:
image: spotify/kafka
container_name: kafka
environment:
ADVERTISED_HOST: kafka
ADVERTISED_PORT: 9092
hostname: kafka
networks:
- mynet
The batch layer is used as the consumer in Kafka, but it doesn't receive any message from queue. If I use "docker run -it --name batch --link kafka:kafka --link es:es --network=mynet tp33/django" instead of docker-compose to set up batch layer, the consumer can receive messages.
Could anyone figure out the difference?
docker apache-kafka
asked Nov 14 at 22:19
Leo
112
add a comment |
up vote
1
down vote
favorite
I am using docker-compose.yml to set up multi-layer web app.
batch:
image: tp33/django
container_name: batch
links:
- kafka:kafka
- es:es
depends_on:
- kafka
- es
volumes:
- ./batch_layer:/app
networks:
- mynet
command: bash -c "cd /app && python consumer.py"
kafka:
image: spotify/kafka
container_name: kafka
environment:
ADVERTISED_HOST: kafka
ADVERTISED_PORT: 9092
hostname: kafka
networks:
- mynet
The batch layer is used as the consumer in Kafka, but it doesn't receive any message from queue. If I use "docker run -it --name batch --link kafka:kafka --link es:es --network=mynet tp33/django" instead of docker-compose to set up batch layer, the consumer can receive messages.
Could anyone figure out the difference?
docker apache-kafka
asked Nov 14 at 22:19
Leo
112
Note: the Spotify image is no longer maintained and is using an old Kafka version
– cricket_007
Nov 15 at 2:21
The primary difference is that you're hard coding the command in the compose file and you're not using interactive mode compared torun -it, but without your Python code, it's hard to really say since this isn't a Minimal, Complete, and Verifiable example
– cricket_007
Nov 15 at 2:23
did you dodocker-compose runordocker-compose up?
– dtheo
Nov 15 at 3:58
I am using docker-compose up. I just fixed the problem by putting the KafkaConsumer() in try-except block and looping until successfully connecting to kafka from batch layer. But I still cannot figure out the difference
– Leo
Nov 16 at 3:09
One thing that you can do is to make sure that kafka is actually fully running before start the command on the batch. You can see an example here docs.docker.com/compose/startup-order that waits for postgresql to be running first
– dtheo
Nov 16 at 4:26
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am using docker-compose.yml to set up multi-layer web app.
batch:
image: tp33/django
container_name: batch
links:
- kafka:kafka
- es:es
depends_on:
- kafka
- es
volumes:
- ./batch_layer:/app
networks:
- mynet
command: bash -c "cd /app && python consumer.py"
kafka:
image: spotify/kafka
container_name: kafka
environment:
ADVERTISED_HOST: kafka
ADVERTISED_PORT: 9092
hostname: kafka
networks:
- mynet
The batch layer is used as the consumer in Kafka, but it doesn't receive any message from queue. If I use "docker run -it --name batch --link kafka:kafka --link es:es --network=mynet tp33/django" instead of docker-compose to set up batch layer, the consumer can receive messages.
Could anyone figure out the difference?
docker apache-kafka
asked Nov 14 at 22:19
Leo
112
I am using docker-compose.yml to set up multi-layer web app.
batch:
image: tp33/django
container_name: batch
links:
- kafka:kafka
- es:es
depends_on:
- kafka
- es
volumes:
- ./batch_layer:/app
networks:
- mynet
command: bash -c "cd /app && python consumer.py"
kafka:
image: spotify/kafka
container_name: kafka
environment:
ADVERTISED_HOST: kafka
ADVERTISED_PORT: 9092
hostname: kafka
networks:
- mynet
The batch layer is used as the consumer in Kafka, but it doesn't receive any message from queue. If I use "docker run -it --name batch --link kafka:kafka --link es:es --network=mynet tp33/django" instead of docker-compose to set up batch layer, the consumer can receive messages.
Could anyone figure out the difference?
docker apache-kafka
docker apache-kafka
asked Nov 14 at 22:19
Leo
112
asked Nov 14 at 22:19
Leo
112
asked Nov 14 at 22:19
Leo
112
asked Nov 14 at 22:19
Leo
112
asked Nov 14 at 22:19
Leo
112
112
Note: the Spotify image is no longer maintained and is using an old Kafka version
– cricket_007
Nov 15 at 2:21
The primary difference is that you're hard coding the command in the compose file and you're not using interactive mode compared torun -it, but without your Python code, it's hard to really say since this isn't a Minimal, Complete, and Verifiable example
– cricket_007
Nov 15 at 2:23
did you dodocker-compose runordocker-compose up?
– dtheo
Nov 15 at 3:58
I am using docker-compose up. I just fixed the problem by putting the KafkaConsumer() in try-except block and looping until successfully connecting to kafka from batch layer. But I still cannot figure out the difference
– Leo
Nov 16 at 3:09
One thing that you can do is to make sure that kafka is actually fully running before start the command on the batch. You can see an example here docs.docker.com/compose/startup-order that waits for postgresql to be running first
– dtheo
Nov 16 at 4:26
add a comment |
Note: the Spotify image is no longer maintained and is using an old Kafka version
– cricket_007
Nov 15 at 2:21
The primary difference is that you're hard coding the command in the compose file and you're not using interactive mode compared torun -it, but without your Python code, it's hard to really say since this isn't a Minimal, Complete, and Verifiable example
– cricket_007
Nov 15 at 2:23
did you dodocker-compose runordocker-compose up?
– dtheo
Nov 15 at 3:58
I am using docker-compose up. I just fixed the problem by putting the KafkaConsumer() in try-except block and looping until successfully connecting to kafka from batch layer. But I still cannot figure out the difference
– Leo
Nov 16 at 3:09
One thing that you can do is to make sure that kafka is actually fully running before start the command on the batch. You can see an example here docs.docker.com/compose/startup-order that waits for postgresql to be running first
– dtheo
Nov 16 at 4:26
Note: the Spotify image is no longer maintained and is using an old Kafka version
– cricket_007
Nov 15 at 2:21
Note: the Spotify image is no longer maintained and is using an old Kafka version
– cricket_007
Nov 15 at 2:21
The primary difference is that you're hard coding the command in the compose file and you're not using interactive mode compared to
run -it, but without your Python code, it's hard to really say since this isn't a Minimal, Complete, and Verifiable example– cricket_007
Nov 15 at 2:23
The primary difference is that you're hard coding the command in the compose file and you're not using interactive mode compared to
run -it, but without your Python code, it's hard to really say since this isn't a Minimal, Complete, and Verifiable example– cricket_007
Nov 15 at 2:23
did you do
docker-compose run or docker-compose up?– dtheo
Nov 15 at 3:58
did you do
docker-compose run or docker-compose up?– dtheo
Nov 15 at 3:58
I am using docker-compose up. I just fixed the problem by putting the KafkaConsumer() in try-except block and looping until successfully connecting to kafka from batch layer. But I still cannot figure out the difference
– Leo
Nov 16 at 3:09
I am using docker-compose up. I just fixed the problem by putting the KafkaConsumer() in try-except block and looping until successfully connecting to kafka from batch layer. But I still cannot figure out the difference
– Leo
Nov 16 at 3:09
One thing that you can do is to make sure that kafka is actually fully running before start the command on the batch. You can see an example here docs.docker.com/compose/startup-order that waits for postgresql to be running first
– dtheo
Nov 16 at 4:26
One thing that you can do is to make sure that kafka is actually fully running before start the command on the batch. You can see an example here docs.docker.com/compose/startup-order that waits for postgresql to be running first
– dtheo
Nov 16 at 4:26
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53309591%2fconsumer-receives-no-message-from-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
Note: the Spotify image is no longer maintained and is using an old Kafka version
– cricket_007
Nov 15 at 2:21
The primary difference is that you're hard coding the command in the compose file and you're not using interactive mode compared to
run -it, but without your Python code, it's hard to really say since this isn't a Minimal, Complete, and Verifiable example– cricket_007
Nov 15 at 2:23
did you do
docker-compose runordocker-compose up?– dtheo
Nov 15 at 3:58
I am using docker-compose up. I just fixed the problem by putting the KafkaConsumer() in try-except block and looping until successfully connecting to kafka from batch layer. But I still cannot figure out the difference
– Leo
Nov 16 at 3:09
One thing that you can do is to make sure that kafka is actually fully running before start the command on the batch. You can see an example here docs.docker.com/compose/startup-order that waits for postgresql to be running first
– dtheo
Nov 16 at 4:26