I have installed 2 brokers on EC2. I also have a (scala) application that receives data stream and pushes to kafka cluster. By co-incidence, a (slightly heavier) EC2 instance is running both a kafka broker and the data receiver application. I am noticing that all data receiver application nodes that are not on the shared kafka + reciever app EC2 instance are complaining for connect errors to localhost.localdomain:9092. Is this a possible bug that results in Kafka detecting instance hostname as localhost.localdomain instead of actual hostname?
Also, how do I fix this temporarily until a permanent fix is available?
I think the FAQ mentions why it's not possible to connect to broker from outside. In my case, all servers (producers and brokers) are in the same VPC. Call to InetAddress.getLocalHost.getHostAddress should return an internal IP to which producers should be able to connect. The issue seems to be that the call to InetAddress.getLocalHost.getHostAddress returns localhost.localdomain and that too on just 1 broker. Any ideas on why that could be happening?
I can configure host.name property in broker config but its slightly painful. I am curious to know what can cause InetAddress.getLocalHost.getHostAddress to return loopback addresses like localhost.localdomain so that other users know why they really have to setup host.name in EC2 even if both producers and consumers are in same VPC. On 3 October 2013 19:56, Jun Rao <[EMAIL PROTECTED]> wrote:
Is there something we could be doing in Kafka to avoid this problem?
-Jay On Thu, Oct 3, 2013 at 8:29 AM, Rajasekar Elango <[EMAIL PROTECTED]>wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext