# Disable fault detection for tribe node

**URL:** <https://discuss.elastic.co/t/disable-fault-detection-for-tribe-node/1155>\
**Category:** Elasticsearch\
**Created:** [May 22, 2015, 7:47am UTC](https://discuss.elastic.co/t/disable-fault-detection-for-tribe-node/1155 "2015-05-22T07:47:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![tktr](https://avatars.discourse-cdn.com/v4/letter/t/eb8c5e/32.png) [@tktr](https://discuss.elastic.co/u/tktr)\
**Post date:** [May 22, 2015, 7:47am UTC](https://discuss.elastic.co/t/disable-fault-detection-for-tribe-node/1155/1 "2015-05-22T07:47:08Z")

</div>

Hi,

I'm wondering if there is a possibility to disable fault detection for tribe nodes. In my current setup I want to create a tribe node and connect to two clusters which are located in different networks. However, it is a requirement that there are no connections initiated to the tribe node. Unfortunately, there need to be open ports on the tribe node due to the **NodesFaultDetection** mechanism. As a tribe node is not required for a cluster to be fully operational it would be nice to disable this mechanism for specific nodes. Is there currently any workaround how I could get this running ?

Thx in advance

---

<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:** [May 24, 2015, 2:24am UTC](https://discuss.elastic.co/t/disable-fault-detection-for-tribe-node/1155/2 "2015-05-24T02:24:03Z")

</div>

This isn't possible, the Tribe node needs to know when a cluster is unavailable to fulfil it's role.

---

<div class="post-metadata">

**Author:** ![tktr](https://avatars.discourse-cdn.com/v4/letter/t/eb8c5e/32.png) [@tktr](https://discuss.elastic.co/u/tktr)\
**Post date:** [May 26, 2015, 7:11am UTC](https://discuss.elastic.co/t/disable-fault-detection-for-tribe-node/1155/3 "2015-05-26T07:11:26Z")

</div>

Thanks for your reply. If my understanding of the fault detection is correct, this should be the handled by **MasterFaultDetection** and not **NodesFaultDetection**. The problem is actually the connections originating from the clusters.

---

<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:** [May 26, 2015, 7:19am UTC](https://discuss.elastic.co/t/disable-fault-detection-for-tribe-node/1155/4 "2015-05-26T07:19:33Z")

</div>

It'd be worth raising this as a Github issue and see what some of the core devs have to say 🙂

---

<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 6, 2017, 12:11am UTC](https://discuss.elastic.co/t/disable-fault-detection-for-tribe-node/1155/5 "2017-07-06T00:11:57Z")

</div>

Closed on July 6, 2017, 12:11am UTC