[rabbitmq-discuss] Open-Ok no longer populating known_hosts
sigurd.hogsbro at museeka.com
Wed Sep 1 13:22:39 BST 2010
We use the hostname for follow-up diagnosis after identifying application
failures. In such scenarios it is useful to know which of the RabbitMQ
servers behind the (transparent) load-balancer to investigate.
Fair point on the information leakage, but I'm not sure why you're concerned
about the server hostname being exposed as it used to be exposed until
recently. We could also use a name/token specified in the server
configuration file if you prefer not to expose DNS names.
Otherwise we'll have to figure a way get this information from the
2010/9/1 Matthias Radestock <matthias at rabbitmq.com>
> On 01/09/10 11:21, Michael Bridgen wrote:
>> A follow-on thought: could you add a key with the server hostname to
>>> the server_properties dict sent back from the server on
>>> connection.start? That would solve our diagnostics needs (and maybe
>>> Aaron's too) without breaking your conformance to the spec.
>> The server properties is more or less a free-form map, so yes, it's
>> certainly possible a hostname (or more likely, a node name including the
>> hostname) could go there.
>> There may be concerns around leaking infrastructural information that
>> way, but probably not strong ones.
> I am reluctant to add ad-hoc properties without a sound technical
> rationale. And yes the information leakage *is* a concern.
> Can you explain what you are trying to do?
> connection.redirect and the known_hosts field got removed because they a)
> duplicate what load balancers do much better, and b) don't work in many
> network setups since they rely on the clients to be able to resolve servers
> by their internal names.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss