Setting up a client node

The master nodes that we have seen previously are the most important for cluster stability. To prevent the queries and aggregations from creating instability in your cluster, client nodes can be used to provide safe communication with the cluster.

Getting ready

You need a working Elasticsearch installation as we described in the Downloading and installing Elasticsearch recipe in this chapter and a simple text editor to change configuration files.

How to do it...

For advance set up of a cluster, there are some parameters that must be configured to define different node types.

These parameters are in the config/elasticsearch.yml file and they can set up a client node with the following steps:

  1. Set up the node as a no master:
            node.master: false 
    
  2. Set up the node to not contain data:
            node.data: false 
    

How it works...

The client node is a special node that works as a proxy/pass thought for the cluster.

Its main advantages are:

  • It can easily kill or remove the cluster without problems, that's not a master, so it doesn't participate in cluster functionalities and it doesn't contain data so there are no data relocations/replication due to its failure
  • Prevent the instability of the cluster due to developers'/users' bad queries. Sometimes a user executes too large aggregations (that is, date histograms with range some years and interval 10 seconds), the Elasticsearch node could crash. The client node is not a master and its overload doesn't give problem to cluster stability.
  • If the client node is embedded in the application, there are less round trips for the data and speeding up the application.
  • You can add them to balance the search and aggregation throughput without generating changes and data relocation in the cluster.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.147.42.129