Hello All, This is my configuration : curl -XGET 172.24.69.19:9200/_cat/nodes : 172.24.69.14 16 36 0 0.00 0.01 0.05 - - es-client-02 172.24.69.18 95 97 20 1.64 1.28 1.25 d - es-data-03 172.24.69.20 15 36 0 0.05 0.05 0.05 m * es-master-02 172.24.69.19 10 36 0 0.02 0.02 0.05 m - es-master-01 …

A tribe node is not the same as a coordinating only node (aka client node). A coordinating node is part of a single cluster and allows both reads and writes, while a tribe node acts as a read-only bridge when searching multiple clusters.

the version is elasticsearch-5.4.0.rpm in my cluster I have 2 logstash server with the following configuration : input { redis { host => "172.24.69.9" data_type => "list" port => "6379" key => "sadra" } redis { host => "172.24.69.10" data_type => "list" port=> "6379" key => "sadra" } …

You don't want tribe nodes. You don't even want cross cluster. Just set up some coordinator nodes like you have - they used to be called client nodes as @Christian_Dahlqvist mentioned :slight_smile:

I don't understand !!!! would you please tell me true configuration . I set this configurations : data nodes : node.name : es-data-* node.master: false node.data: true node.ingest: false discovery.zen.ping.unicast.hosts: ["172.24.69.16","172.24.69.17","172.24.69.18","172.24.69.19","172.24.69.…

As master election is based on consensus, you should always aim to have 3 master-eligible nodes in the cluster and set'discovery.zen.minimum_master_nodes to 2 as per these recommendations .

would you please tell me whats is the problem on coordinator nodes ? why my cluster just see one node ?

What is the output from the cat nodes API , from master node as well as the coordinating nodes?

[root@es-data-01 ~]# curl -XGET http://172.24.69.16:9200/_cat/nodes 172.24.69.16 97 98 19 0.64 0.86 1.06 d - es-data-01 172.24.69.13 11 36 0 0.00 0.01 0.05 - - es-client-01 172.24.69.19 19 36 0 0.01 0.02 0.05 m - es-master-01 172.24.69.20 26 37 1 0.08 0.07 0.06 m * es-master-02 172.24.69.18 …

Are the remaining nodes running? Is there anything in the logs on these nodes that explain this? Are you able to telnet to port 9300 on all the other hosts from these hosts?

Discuss the Elastic Stack

Limitation of client node (Tribe node)

Elastic Stack Elasticsearch

Christian_Dahlqvist (Christian Dahlqvist) September 19, 2017, 5:07am 14

How did you install Elasticsearch on the nodes? Could be having an issue similar to this thread?

Topic		Replies	Views
Client node vs tribe node Elasticsearch	7	2465	July 5, 2017
Tribe nodes Elasticsearch	9	510	July 6, 2017
Using tribe node for federation between Elasticsearch clusters Elasticsearch	4	1388	July 5, 2017
Issues setting up Tribe node Elasticsearch	3	492	July 5, 2017
Tribe node configuration issues Elasticsearch	6	1685	July 5, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Limitation of client node (Tribe node)

Related topics