# Limitation of client node (Tribe node) **URL:** \ **Category:** Elasticsearch\ **Created:** [September 17, 2017, 11:30am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790 "2017-09-17T11:30:21Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![Amin1](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@Amin1](https://discuss.elastic.co/u/Amin1)\ **Post date:** [September 17, 2017, 11:30am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/1 "2017-09-17T11:30:22Z")
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 172.24.69.16 98 97 20 1.11 0.93 1.13 d - es-data-01 172.24.69.17 98 98 10 0.60 0.61 0.68 d - es-data-02 I add another Tribe node to load balance data that come from my logstashes and another Tribe node to connect kibana to it. I think that we have limitation in this nodes , as you see cluster work only with one triger node, is this true or i have mistake in configuration Best ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [September 18, 2017, 6:21am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/2 "2017-09-18T06:21:38Z")
What version are you on? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 18, 2017, 6:28am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/3 "2017-09-18T06:28:51Z")
A [tribe node](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/modules-tribe.html) is not the same as a [coordinating only node](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/modules-node.html#coordinating-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. ---
**Author:** ![Amin1](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@Amin1](https://discuss.elastic.co/u/Amin1)\ **Post date:** [September 18, 2017, 7:33am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/4 "2017-09-18T07:33:28Z")
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" } } output { elasticsearch { hosts =\> ["172.24.69.13:9200","172.24.69.14:9200"] I get logs from two broker and sent it to Elastic triger node with the following ips: 172.24.69.13 172.24.69.14 all elasticsearches version's is : 5.4.0. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [September 18, 2017, 7:36am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/5 "2017-09-18T07:36:36Z")
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 🙂 ---
**Author:** ![Amin1](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@Amin1](https://discuss.elastic.co/u/Amin1)\ **Post date:** [September 18, 2017, 7:58am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/6 "2017-09-18T07:58:53Z")
I don't understand !!!! would you please tell me true configuration . I set this configurations : ## data nodes : [node.name](http://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.20","172.24.69.13","172.24.69.14","172.24.69.21"] network.host: 172.24.69.17 [cluster.name](http://cluster.name): logserver ## master nodes : [cluster.name](http://cluster.name): logserver [node.name](http://node.name): es-master-\* node.master: true node.data: false node.ingest: false network.host: 172.24.69.20 discovery.zen.ping.unicast.hosts: ["172.24.69.21","172.24.69.16","172.24.69.17","172.24.69.18","172.24.69.19","172.24.69.20","172.24.69.13","172.24.69.14"] ## triger nodes : [node.name](http://node.name): es-client-0\* node.master: false node.data: false node.ingest: false [cluster.name](http://cluster.name): logserver discovery.zen.ping.unicast.hosts: ["172.24.69.21",172.24.69.16","172.24.69.17","172.24.69.18","172.24.69.19","172.24.69.20","172.24.69.13","172.24.69.14"] I have 2 master,3 data node , 3 client node my issue is that my cluster just see only one client node and when i shutdown this node, another client node comes to cluster . please tell me is this configuration is true and whats is my main problem ? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 18, 2017, 8:12am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/7 "2017-09-18T08:12:14Z")
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](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/important-settings.html#minimum_master_nodes). ---
**Author:** ![Amin1](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@Amin1](https://discuss.elastic.co/u/Amin1)\ **Post date:** [September 18, 2017, 8:14am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/8 "2017-09-18T08:14:19Z")
would you please tell me whats is the problem on coordinator nodes ? why my cluster just see one node ? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 18, 2017, 8:16am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/9 "2017-09-18T08:16:00Z")
What is the output from the [cat nodes API](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/cat-nodes.html), from master node as well as the coordinating nodes? ---
**Author:** ![Amin1](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@Amin1](https://discuss.elastic.co/u/Amin1)\ **Post date:** [September 18, 2017, 8:18am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/10 "2017-09-18T08:18:32Z")
[root@es-data-01 ~]# curl -XGET [http://172.24.69.16:9200/\_cat/nodes](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 98 98 19 1.19 1.04 1.15 d - es-data-03 ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 18, 2017, 8:21am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/11 "2017-09-18T08:21:17Z")
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? ---
**Author:** ![Amin1](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@Amin1](https://discuss.elastic.co/u/Amin1)\ **Post date:** [September 18, 2017, 8:35am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/12 "2017-09-18T08:35:03Z")
> [@Christian\_Dahlqvist](#): > > remaining nodes running ## yes i telnet to all of them and if I shutdown es-client-01node, another coordinator nodes come to cluster, is there any configuration that limit coordinator node ? [root@es-client-01 ~]# telnet 172.24.69.14 Trying 172.24.69.14... telnet: connect to address 172.24.69.14: Connection refused [root@es-client-01 ~]# telnet 172.24.69.14 9300 Trying 172.24.69.14... Connected to 172.24.69.14. Escape character is '^]'. ## Connection closed by foreign host. [root@es-client-01 ~]# telnet 172.24.69.21 9300 Trying 172.24.69.21... Connected to 172.24.69.21. Escape character is '^]'. ## Connection closed by foreign host. [root@es-client-01 ~]# shutdown when i shutdown this node another one comes to cluster : [root@es-data-01 ~]# curl -XGET [http://172.24.69.16:9200/\_cat/nodes](http://172.24.69.16:9200/_cat/nodes) 172.24.69.16 99 98 15 0.75 0.91 0.99 d - es-data-01 172.24.69.14 19 36 0 0.02 0.02 0.05 - - es-client-02 172.24.69.19 9 36 0 0.00 0.02 0.05 m - es-master-01 172.24.69.20 28 37 1 0.08 0.04 0.05 m \* es-master-02 172.24.69.18 98 98 17 0.60 0.90 1.07 d - es-data-03 ---
**Author:** ![Amin1](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@Amin1](https://discuss.elastic.co/u/Amin1)\ **Post date:** [September 19, 2017, 3:24am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/13 "2017-09-19T03:24:39Z")
Hellowould you please help me and continue topic thanks ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 19, 2017, 5:07am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/14 "2017-09-19T05:07:03Z")
How did you install Elasticsearch on the nodes? Could be having an issue similar to [this thread](https://discuss.elastic.co/t/missing-client-nodes-in-v5-6/100464)? ---
**Author:** ![Amin1](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@Amin1](https://discuss.elastic.co/u/Amin1)\ **Post date:** [September 19, 2017, 6:13am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/15 "2017-09-19T06:13:16Z")
I downloaded rpm file from [elastic.co](http://elastic.co) and install it with the following command : yum localinstall elas.rpm > > Christian\_Dahlqvist Elastic Team Member > > September 19 | How did you install Elasticsearch on the nodes? Visit Topic or reply to this email to respond. In Reply To > > Amin1 Amin > > September 19 | Hellowould you please help me and continue topic thanks Visit Topic or reply to this email to respond. To unsubscribe from these emails, click here. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 17, 2017, 6:13am UTC](https://discuss.elastic.co/t/limitation-of-client-node-tribe-node/100790/16 "2017-10-17T06:13:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.