master and data node

[pccwglobalit]

we have four nodes and the node status is the following
nls1-xxx.logserver.com 172.16.82.24 52 68 0.58 d m 3a9a3cab-0971-4b03-b2d4-d4f2ea4d0b5b
nls3-xxx.logserver.com 172.16.19.10 63 64 0.80 d m 33c658b5-db74-480c-bb71-32c430f77b00
nls1-abc.logserver.com 172.16.7.10 57 60 3.80 d * 181841a1-d717-437c-bd36-6d4a8344abe6
nls1-cde.logserver.com 172.16.1.3 88 71 10.10 d m 41ae2858-4896-4233-8049-1912a47d09e9

the nls1-cde config is very weak and can we fix two master node and other will run data node?

[jolson]

In the above post, you only have one master node - the one marked with an asterisk *. The other nodes marked 'm' are eligible to be master nodes, so they could take over if the primary failed.

the nls1-cde config is very weak and can we fix two master node and other will run data node?

I am not quite sure what you're asking here - do you want to have two dedicated master nodes and make the rest of them data nodes only? We can definitely do this, but do we have a reason to?

[pccwglobalit]

thanks.
The existing master server is not stable (hardware issue). Could we dedicate one or two master server?

[jolson]

The existing master server is not stable (hardware issue). Could we dedicate one or two master server?

Currently all of your nodes are capable of becoming the master node, and if your current master were to fail, one of the others would pick up automatically. You should not have to make any configuration changes.

If you are looking for more precise control over master election settings, the following parameters exist for you to configure in /usr/local/nagioslogserver/elasticsearch/config/elasticsearch.yml:

Code: Select all

# You can exploit these settings to design advanced cluster topologies.
#
# 1. You want this node to never become a master node, only to hold data.
#    This will be the "workhorse" of your cluster.
#
# node.master: false
# node.data: true
#
# 2. You want this node to only serve as a master: to not store any data and
#    to have free resources. This will be the "coordinator" of your cluster.
#
# node.master: true
# node.data: false
#
# 3. You want this node to be neither master nor data node, but
#    to act as a "search load balancer" (fetching data from nodes,
#    aggregating results, etc.)
#
# node.master: false
# node.data: false

Simply uncomment the appropriate pair of configuration parameters and restart elasticsearch:

Code: Select all

service elasticsearch restart

I hope this answers your question. Thanks!

[pccwglobalit]

thanks and i will try.
by the way, what is master and data difference? is that data only store the data but no processing the index?

[jolson]

Data nodes are responsible for the storage of information, processing queries, etc. Anything data-intensive, for the most part.

Master nodes organize where data is sent in the cluster, and how it's all linked together - in general, you can think of master nodes as 'operational' nodes. Pure master nodes store no log data.

I suggest leaving on the default settings unless you're having trouble. NLS is already fault tolerant and reliable, and I wouldn't recommend changing the configurations unless you're confident about the changes you're implementing.

You can read more about node types here: http://www.elastic.co/guide/en/elastics ... -node.html

[pccwglobalit]

ok. thanks for your help

[jolson]

No problem. If you run into any issues feel free to open a new thread - I'll lock this one up. Thanks!