Closed tpolekhin closed 4 years ago
This would be good to-do when we move to the new HTTP API and also move to supporting new Mesos features too. This should be near top of lists to-do with that imho.
Also, it will be very helpful to have ADVERTISED_PORT
from broker config to go into discoveryInfo as well, so we can build some proxying on top of that info.
Mesos provides a mechanism for service discovery applications to get the information for specific tasks, for example ports that are used and protocols. Right now kafka framework doesn't use this. I would be really helpful to have this information per broker added, especially now when Kafka 0.9.0.0 supports SSL on a different port.
Example:
broker-1
withplaintext
for broker-to-broker communication andSSL
forproducers
andconsumers
, andJMX
endpoint for monitoring Kafka with some app inside the cluster