kafka brokers bind to many networks, does it work?


kafka brokers bind to many networks, does it work?



what if a cluster is bind to more than one subnet with different ip addresses for every broker, a dns name for every ip addr. ? This is inside the overall company network (dns included), no exposure to public network. No routing among subnets.
Is it possible to configure the cluster in order to not make a mess and respect configured networking?
I mean, I configure listeners with the names of the internal subnet (the one with kafka brokers and zookeeper servers) and external listeners with the names of every subnet the broker is bind to.
Supposed configuration (part of):


advertised.listeners=EXTERNAL://broker1.subnet1.localdomain:9993,EXTERNAL://broker2.subnet1.localdomain:9993,EXTERNAL://broker1.subnet2.localdomain:9993,EXTERNAL://broker2.subnet2.localdomain:9993,EXTERNAL://broker1.subnet3.localdomain:9993,EXTERNAL://broker2.subnet3.localdomain:9993,INTERNAL://broker1.internalsubnet.localdomain:9990
inter.broker.listener.name=INTERNAL
listener.security.protocol.map=EXTERNAL:SSL,INTERNAL:PLAINTEXT



Make sense?









By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Comments

Popular posts from this blog

paramiko-expect timeout is happening after executing the command

Opening a url is failing in Swift

Export result set on Dbeaver to CSV