[jira] [Commented] (KAFKA-1945) MetaData Response - Broker hostname is wrong

["Manikumar Reddy (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315841#comment-14315841 ] 

Manikumar Reddy commented on KAFKA-1945:
----------------------------------------

You can set "host.name" , "advertised.host.name"  server config properties to bind a particular host name.
https://cwiki.apache.org/confluence/display/KAFKA/FAQ#FAQ-Whycan'tmyconsumers/producersconnecttothebrokers?

Also pl post such kind of questions to mailing list (https://kafka.apache.org/contact.html)

> MetaData Response - Broker hostname is wrong
> --------------------------------------------
>
>                 Key: KAFKA-1945
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1945
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>            Reporter: saravana kumar
>
> I use python-kafka's SimpleConsumer to listen to a topic in kafka broker. Kafka broker is running on a machine with its hostname as BROKER_HOST. Now, SimpleConsumer from another machine requests for topic metadata from the broker BROKER_HOST for a topic TOPIC & gets a python tuple
>    (Broker metadata, Topic metadata)
> Broker metadata comes as,
>  {0: BrokerMetadata(nodeId=0, host='localhost', port=9092)}
> ideally, host value must be BROKER_HOST("hostname" cmd from broker shell tty confirms it) but it comes as localhost...
> How does the wrong broker metadata for a topic get into kafka system? And obviously, this breaks the system since my consumer tries to connect to 9092 on its localhost.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)