Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--bind-address for broker seems to be ignored #197

Closed
IngoS11 opened this issue Apr 4, 2016 · 7 comments
Closed

--bind-address for broker seems to be ignored #197

IngoS11 opened this issue Apr 4, 2016 · 7 comments
Labels

Comments

@IngoS11
Copy link

IngoS11 commented Apr 4, 2016

Hi everyone,
I am using Kafka 0.9.0.1 trying to get my kafka brokers to bind to only one specific interface. So far I had no luck with it. Regardless of trying a specific IP address via --bind-address 192.168.0.* or via an interface via --bind-address if:bond0.1401 when the broker starts up I can see that it is still bound to every interface and the brokers in Zookeeper advertise themselves under the wrong hostname/domain. Has anybody managed to get brokers to listen to a specific IP and get that advertised in Zookeeper?

@IngoS11
Copy link
Author

IngoS11 commented Apr 6, 2016

Short update: I beleive this is a Kakfa 0.9.0.1 issue. I played with a plain Kafka locally and I cannot make Kafka bind to only one interface with the property host.name=. It always binds to all interfaces available. I also noticed that unless you explicitly specify advertised.host.name Kafka 0.9.0.1 uses the hostnname that is resolved during startup of a broker. Ironically this is in contrast to what is given as description in the properties files right above advertised.host.hame where they say that unless you specify it it makes use of what you specify in the host.name entry.

I am now wondering if there is a way to pass on the advertised.host.name dynamically via the framework?

@joestein
Copy link
Contributor

yeah it should be on the advertised host and shouldn't be a problem for backwards comptable

@joestein joestein added the bug label Apr 15, 2016
@yu2003w
Copy link

yu2003w commented Nov 28, 2016

@joestein
I have found the problem code. After some basic testing, I could run latest kafka with this framework.
I want to fix this problem. Which process should I follow?

@xiaods
Copy link

xiaods commented Nov 29, 2016

add a pr first.

@yu2003w
Copy link

yu2003w commented Dec 9, 2016

@xiaods @joestein
PR #259 was created. Please have a look and invite guys to review.
Any problem please let me know.

@yu2003w
Copy link

yu2003w commented Jan 26, 2017

PR#259 was merged into master branch, so please verify and close this issue.

@xiaods
Copy link

xiaods commented Feb 10, 2017

@yu2003w thanks for your at.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants