# Tribe node setup with a remote multi-node cluster

**URL:** <https://discuss.elastic.co/t/tribe-node-setup-with-a-remote-multi-node-cluster/40050>\
**Category:** Elasticsearch\
**Created:** [January 25, 2016, 5:50pm UTC](https://discuss.elastic.co/t/tribe-node-setup-with-a-remote-multi-node-cluster/40050 "2016-01-25T17:50:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![vpoliboy](https://avatars.discourse-cdn.com/v4/letter/v/898d66/32.png) [@vpoliboy](https://discuss.elastic.co/u/vpoliboy)\
**Post date:** [January 25, 2016, 5:50pm UTC](https://discuss.elastic.co/t/tribe-node-setup-with-a-remote-multi-node-cluster/40050/1 "2016-01-25T17:50:11Z")

</div>

We are trying to setup a tribe node that connects to a remote single master multi-node cluster. The constraints we have right now is that the tribe node has connectivty to the master node only because of issues like firewall configuration, VPN set up and other issues. Since a tribe node creates a node client and tries to connect to all the nodes in the cluster, there are transport exceptions because of the connectivity issues with the cluster data nodes but we observed that

1. Elasticsearch reads(search/gets) from the tribe node are working fine.
2. Writes to the indices on the cluster mostly work fine but I have seen random failures.

The question is it okay to have this setup (tribe node connectivity to only the master node of the cluster) as our problem domain involves almost all reads or do you see any other potential fatal issues?

---

<div class="post-metadata">

**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:** [January 26, 2016, 1:48am UTC](https://discuss.elastic.co/t/tribe-node-setup-with-a-remote-multi-node-cluster/40050/2 "2016-01-26T01:48:44Z")

</div>

> [@vpoliboy](#):
>
> The question is it okay to have this setup

Well it's not ideal due to the networking issues, but if it works for you....

---

<div class="post-metadata">

**Author:** ![unknownunknown](https://avatars.discourse-cdn.com/v4/letter/u/4da419/32.png) [@unknownunknown](https://discuss.elastic.co/u/unknownunknown)\
**Post date:** [February 11, 2016, 5:22pm UTC](https://discuss.elastic.co/t/tribe-node-setup-with-a-remote-multi-node-cluster/40050/3 "2016-02-11T17:22:16Z")

</div>

> [@vpoliboy](#):
>
> Since a tribe node creates a node client and tries to connect to all the nodes in the cluster, there are transport exceptions because of the connectivity issues with the cluster data nodes but we observed that

Is there any way to disable this behavior?

For example, is this the same thing as sniffing, as mentioned here?

> "...can you try and remove sniffing please? I am afraid that it will make  
> the transport client point to the tribe node plus all of the different  
> nodes in the two clusters, which would explain your mixed results."

> <https://github.com/elastic/elasticsearch/issues/15928>
>
> Hi! I am using a tribe node with the transport client to connect to 2 clusters. …When I look at \*\*\_cat/indices\*\* I see consistent indexes. When I use the transport client with the below \*\*does the specified index exist?\*\* request I get true 50% of the time and false 50% of the time although the index does in fact exist.
> 
> Code:
> 
> \`\`\` java
> public boolean indexExists(String index, TransportClient client) {
> return client.admin().indices().exists(new IndicesExistsRequest(index)).actionGet().isExists();
> }
> \`\`\`
> 
> YML settings:
> 
> \`\`\`
> tribe:
> t1:
> cluster.name: clusterone
> discovery.zen.ping.multicast.enabled: false
> discovery.zen.ping.unicast.hosts: clusterone-master-a,clusterone-master-b,clusterone-master-c
> t2:
> cluster.name: clustertwo
> discovery.zen.ping.multicast.enabled: false
> discovery.zen.ping.unicast.hosts: clustertwo-master-a,clustertwo-master-b,clustertwo-master-c
> \`\`\`

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:17pm UTC](https://discuss.elastic.co/t/tribe-node-setup-with-a-remote-multi-node-cluster/40050/4 "2017-07-05T23:17:03Z")

</div>