autodiscovery not working in multi-node single-host installation

elastic / elasticsearch-cloud-aws

AWS Cloud Plugin for Elasticsearch

https://github.com/elastic/elasticsearch/tree/master/plugins/discovery-ec2

577 stars 180 forks source link

autodiscovery not working in multi-node single-host installation #197

Closed uwebartels closed 9 years ago

uwebartels commented 9 years ago

Hiho,

I probably have a quite special installation. I'm running es-1.4.4 cluster on a single machine with

one node: node0 with the role master only for loadbalancing and split-brain-problem
two nodes: node1 and node2 with the roles master+data each as the workhorses When I start node1 first, then all the other nodes I have a complete cluster running with node1 bound to port 9300. The others bound to port 9301 and 9302.

now I try to code a rolling restart.

When I restart node1 first then node1 starts up successfully but doesn't find the other nodes on the same machine bound to port 9301 and 9302.

Is there a way to get this working? I know this is a special kind of installation that doesn't makes sense on aws, but aws is my testbed for other installations using zen discovery.

Thanks, Uwe

jerry4 commented 9 years ago

I think your issue is similar to #99 (closed without fix) and elastic/elasticsearch#7090 (still open, but there is a pull request associated). I ended up forking and adding that fix into my own local branch.

Hope this helps (and that the number of ports to scan becomes configurable at some point).

Jerry

uwebartels commented 9 years ago

Hi, Jerry,

good to know that it doesn't work right now. yesterday coded and tested that in my production environment. not nice, but our environment does not have need that high availability yet.

Best... Uwe

Am 28/4/2015 um 23:15 schrieb jerry4:

I think your issue is similar to #99 https://github.com/elastic/elasticsearch-cloud-aws/issues/99 (closed without fix) and elastic/elasticsearch#7090 https://github.com/elastic/elasticsearch/issues/7090 (still open, but there is a pull request associated). I ended up forking and adding that fix into my own local branch.

Hope this helps (and that the number of ports to scan becomes configurable at some point).

Jerry

— Reply to this email directly or view it on GitHub https://github.com/elastic/elasticsearch-cloud-aws/issues/197#issuecomment-97209334.

dadoonet commented 9 years ago

This won't be fix in this plugin but in elasticsearch core itself. See https://github.com/elastic/elasticsearch/pull/8833.

Closing.