Node

A node is a single instance of the Elasticsearch server and it can host data. This means that shards of indices are allowed to be allocated on the nodes. By default, each node is considered to be a data node, but you can turn the setting off.

Note

You can make a non-data node by adding node.data: false to the elasticsearch.yml file.

Non-data nodes

There are two types of non-data nodes: dedicated master nodes and client nodes.

Dedicated master nodes

Dedicated master nodes will have the settings node.data: false and node.master :true. Such nodes are responsible for managing the cluster. Index and search requests are not sent to these nodes.

Client nodes

Client nodes will have the settings node.data: false and node.master: false. It can be used to balance the load because all HTTP communication will be performed through these nodes.

Tribe node

Another type of Elasticsearch node is tribe node. Normally, a node is associated with a single cluster. But sometimes, all the connected clusters may feel the need to get information. In other words, you may want to access data from multiple clusters. The tribe nodes respond to this need. A tribe node acts as a federated client across multiple clusters. The tribe node works to retrieve the state of all connected clusters and merges them into a global cluster state:

tribe:
    appellation1:
        cluster.name: cluster_user
    appellation2:
        cluster.name: cluster_employee

When configuring a tribe node, it just needs to list the clusters that should be joined. The appellation1 and appellation2 are arbitrary names representing the connection to each 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.56.45