Since I have a 4 node cluster, and have the potential of having any of the 4 become the 'master'
Does this make sense? An even number of systems allows for the 'split brain' problem.
Should I designate 3 as potential masters and have the 4th just be a data node?
Another question from inside the elasticsearch.yml file
I see the following line:
discovery.zen.ping.unicast.hosts: ["localhost"]
Should that instead be:
discovery.zen.ping.unicast.hosts: ["node1", "node2", "node3"]
Please advise. It works as is, but you know...
Thanks
Steve B
NLS Cluster question
-
SteveBeauchemin
- Posts: 524
- Joined: Mon Oct 14, 2013 7:19 pm
NLS Cluster question
XI 5.7.3 / Core 4.4.6 / NagVis 1.9.8 / LiveStatus 1.5.0p11 / RRDCached 1.7.0 / Redis 3.2.8 /
SNMPTT / Gearman 0.33-7 / Mod_Gearman 3.0.7 / NLS 2.0.8 / NNA 2.3.1 /
NSClient 0.5.0 / NRPE Solaris 3.2.1 Linux 3.2.1 HPUX 3.2.1
SNMPTT / Gearman 0.33-7 / Mod_Gearman 3.0.7 / NLS 2.0.8 / NNA 2.3.1 /
NSClient 0.5.0 / NRPE Solaris 3.2.1 Linux 3.2.1 HPUX 3.2.1
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: NLS Cluster question
If you did this in theory you could still get a split brain problem as any of the 3 that are designated master capable could become master leaving the potential for 2 of them to be designated as master..SteveBeauchemin wrote:Since I have a 4 node cluster, and have the potential of having any of the 4 become the 'master'
Does this make sense? An even number of systems allows for the 'split brain' problem.
Should I designate 3 as potential masters and have the 4th just be a data node?
In practice we haven't seen this materialize but the only real way around it would be to designate several nodes as master and make the data node NOT able to be master (with no data).
For licensing, the nodes you pay to license are the data nodes, so actually, you could leave 4 data nodes and have several other nodes used as designated masters.
This actually gets overridden when you start the service, from the includedSteveBeauchemin wrote:I see the following line:
discovery.zen.ping.unicast.hosts: ["localhost"]
Should that instead be:
discovery.zen.ping.unicast.hosts: ["node1", "node2", "node3"]
Please advise. It works as is, but you know...
/etc/sysconfig/elasticsearch
the bottom of that script sets ES_JAVA_OPTS after running
Code: Select all
php $APP_DIR/scripts/get_es_config.php-
SteveBeauchemin
- Posts: 524
- Joined: Mon Oct 14, 2013 7:19 pm
Re: NLS Cluster question
Thank you for the info Scott. It's good stuff.
You can close this.
Steve B
You can close this.
Steve B
XI 5.7.3 / Core 4.4.6 / NagVis 1.9.8 / LiveStatus 1.5.0p11 / RRDCached 1.7.0 / Redis 3.2.8 /
SNMPTT / Gearman 0.33-7 / Mod_Gearman 3.0.7 / NLS 2.0.8 / NNA 2.3.1 /
NSClient 0.5.0 / NRPE Solaris 3.2.1 Linux 3.2.1 HPUX 3.2.1
SNMPTT / Gearman 0.33-7 / Mod_Gearman 3.0.7 / NLS 2.0.8 / NNA 2.3.1 /
NSClient 0.5.0 / NRPE Solaris 3.2.1 Linux 3.2.1 HPUX 3.2.1
Re: NLS Cluster question
Locking.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.