On 5.6.4
Why is it that I cannot list each nodes' OWN IP in:
discovery.zen.ping.unicast.hosts:
?
If I do this, (e.g. give every node in cluster same entry for "discovery.zen.ping.unicast.hosts: " ), then the cluster comes up red.
Why is ES so finnicky about this? (and forces me to script more for the setup)
warkolm
(Mark Walkom)
December 4, 2017, 8:29pm
2
It shouldn't be a problem.
Perhaps if you share some logs we can check what is happening?
I am happy to share logs, but they don't say anything... (they show no errors)
The situation is:
Two ES servers, intent is to cluster them. Machines are: 192.168.10.33 and 192.168.10.34
On the .33 system, I can do:
discovery.zen.ping.unicast.hosts: ["192.168.10.34"]
If I do, on both nodes:
discovery.zen.ping.unicast.hosts: ["192.168.10.33", "192.168.10.34"]
The cluster health is red.
I can only get cluster health to green if .33 points to .34, and .34 points to .33
It would be nice to have a more vanilla way to go.
Open to suggestions!
warkolm
(Mark Walkom)
December 4, 2017, 9:55pm
4
Right, but they will show something, so it'd be useful
system
(system)
Closed
January 1, 2018, 10:07pm
5
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.