# Tribe node - performance cost?

**URL:** <https://discuss.elastic.co/t/tribe-node-performance-cost/16312>\
**Category:** Elasticsearch\
**Created:** [March 12, 2014, 7:57am UTC](https://discuss.elastic.co/t/tribe-node-performance-cost/16312 "2014-03-12T07:57:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DH1](https://avatars.discourse-cdn.com/v4/letter/d/65b543/32.png) [@DH1](https://discuss.elastic.co/u/DH1)\
**Post date:** [March 12, 2014, 7:57am UTC](https://discuss.elastic.co/t/tribe-node-performance-cost/16312/1 "2014-03-12T07:57:07Z")

</div>

Hi, everyone.

I have a few questions regarding that new feature, the tribe nodes.  
It seems, at first glance, incredibly usefull, offering great scalability.  
(why would I bring new nodes to my cluster, when I can bring a whole new  
cluster instead?)

What I'm worried about is the performance cost of using such a node.  
In our project, here, we have a really big cluster, full of really  
complicated documents. (many fields, collections and sub-collection).  
There are actually two kinds of docs, and we never have to request on the  
two kinds at the same time. However, to request on those documents, we need  
info (I'll call them "metadata") located in the cluster.

Thats why I'm currently considering splitting my cluster in 3. Two big ones  
(data 1 and data 2) and a small one (metadata).  
That would, I think, increase the availability of my data. If data 1 were  
to fail, I could still request on data 2, so only half of my application  
would be inaccessible.

However, I'm wondering about the tribe node .. must it be powerfull? More  
than or less than my data nodes?  
And, more importantly, the requests need to be fast (and boy, are they  
fast) .. would the use of a tribe node slows them?  
Does anyone have any experience to share with that feature?

Thanks,  
Deny

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/25c67ca4-a0b5-4d70-9072-6be976840c0b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/25c67ca4-a0b5-4d70-9072-6be976840c0b%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 1:43am UTC](https://discuss.elastic.co/t/tribe-node-performance-cost/16312/2 "2017-07-06T01:43:58Z")

</div>