Comment 25 for bug 822979

On Tue, May 6, 2014 at 6:09 PM, Curtis Hovey <email address hidden> wrote:
> The cluster problem may relate to bug 1294202.

Isn't that bug against the current elasticsearch charm (which uses
autodiscovery)? The version I've got here intentionally does not use
autodiscovery, instead using the peer relation (so it can work in any
environment whether multicast is supported or not).

That said, I'd still like to test what happens if another ES unit on
the same network is started with the same cluster name with
autodiscovery on (ie. will it add the units, even though they have
autodiscovery off themselves... I'd guessing so, which is still
dangerous), add firewall rules or similar so that the units can only
talk to peers on 9400. Auto-generating the clustername is a good idea
too, but would still allow malicious users to set the cluster name
intentionally.