Skip to content
This repository has been archived by the owner on Nov 28, 2023. It is now read-only.

Kafka experiences host resolution issues in private EC2 instances

Jump to bottom
Jason Dugdale edited this page Jan 31, 2017 · 1 revision

We have received reports of receiving Connection Refused errors when trying to connect to the Kafka instance when running the Connector in a private EC2 instance.

Some workarounds for this issue would be:

  1. Add line to /opt/kafka/config/server.properties:
host.name=127.0.0.1
  1. Restart Kafka, Reader and Writer:
supervisorctl restart kafka
supervisorctl restart gnip-reader
supervisorctl restart datasift-writer

Alternatively:

  1. Add line to /etc/hosts:
127.0.0.1 <Your internal EC2 hostname, such as ip-172-00-0-000.ec2.internal>
  1. Restart Kafka, Reader and Writer:
supervisorctl restart kafka
supervisorctl restart gnip-reader
supervisorctl restart datasift-writer
Clone this wiki locally