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
Comments
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? |
yeah it should be on the advertised host and shouldn't be a problem for backwards comptable |
@joestein |
add a pr first. |
PR#259 was merged into master branch, so please verify and close this issue. |
@yu2003w thanks for your at. |
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?The text was updated successfully, but these errors were encountered: