Hi Oliver, I am not familiar with OpenNebula cloud, but in AWS the internal private IP address is usually different from its public IP address:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-ip-addressing.html Maybe OpenNebula has the same settings? Guozhang On Tue, Apr 26, 2016 at 10:06 AM, Oliver Pačut <oliver.pa...@gmail.com> wrote: > Hello, > > I am trying to run a simple kafka cluster on an OpenNebula cloud. I am > using the 0.9.0. Kafka binary. Each time I try to connect to the broker > (from localhost or from a different machine), I get this error: > > [kafka-producer-network-thread | producer-1] DEBUG > o.apache.kafka.clients.NetworkClient - Sending metadata request > ClientRequest(expectResponse=true, callback=null, > > request=RequestSend(header={api_key=3,api_version=0,correlation_id=7,client_id=producer-1}, > body={topics=[test2]}), isInitiatedByNetworkClient, > createdTimeMs=1461688260916, sendTimeMs=0) to node -1 > [kafka-producer-network-thread | producer-1] WARN > o.apache.kafka.clients.NetworkClient - Error while fetching metadata with > correlation id 7 : {test2=LEADER_NOT_AVAILABLE} > > my zookeeper configuration file is unchanged from default (only the data > path) and my server configuration is different in these fields: > > port = 9090 > host.name = <IP address without port> > > The zookeeper and the server are both running on the same nachine. I > unlocked firewall ports 2181 and 9090 both. The producer and consumer are > configured correctly, as they worked on a different system (my home > laptop). Am I missing some important configuration? > > Thanks in advance, > > Oliver Pacut > -- -- Guozhang
