Comment 23 for bug 822979

On Tue, May 6, 2014 at 5:07 PM, Whit Morriss <email address hidden> wrote:
> Hey micheal, was playing a bit and noticed some flakiness around adding
> peers. Is there some reason no to let elasticsearch do auto-discovery
> and use the cluster name to avoid unwanted cluster joins?

Hi Whit, thanks for digging in there.

Can you give me steps to reproduce the flakiness? I'd love to get that sorted.

The elasticsearch autodiscovery is dependent on multicast which isn't
generally available. Different services have their own way of enabling
something similar, but I'd really like to have the charm doing one
thing that works (and is tested) on any service provider, rather than
using one plugin for ec2, something else for HP Cloud etc. Given that
juju is already providing the peer IPs, it seemed like the sane thing
to do.

As above, I'd love to debug and fix the flakiness that you're seeing
(the tests include testing a 3 unit deploy). Thanks!