# ElasticSearch deployment architecture with tribe nodes

**URL:** <https://discuss.elastic.co/t/elasticsearch-deployment-architecture-with-tribe-nodes/20392>\
**Category:** Elasticsearch\
**Created:** [October 23, 2014, 3:37am UTC](https://discuss.elastic.co/t/elasticsearch-deployment-architecture-with-tribe-nodes/20392 "2014-10-23T03:37:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Connie\_Yang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/connie_yang/32/1167_2.png) [@Connie\_Yang](https://discuss.elastic.co/u/Connie_Yang)\
**Post date:** [October 23, 2014, 3:37am UTC](https://discuss.elastic.co/t/elasticsearch-deployment-architecture-with-tribe-nodes/20392/1 "2014-10-23T03:37:06Z")

</div>

Hi,

I want to setup an ELK Stack infrastructure that streams the logs from two  
data centers and make the combined log viewable through a single Kibana  
console. Each data center has a local ElasticSearch cluster. So, I'm  
considering using Tribe nodes to bring the data together.

The questions are

- Because I want to setup the tribe nodes with HA and DR in mind, I'm  
considering putting two tribe nodes in each data center. Do you see any  
problem with this setup? Any special config I need to be aware of besides  
the one that's already been mentioned in tribe node blog?
- Tribe node documentation mentions that multicast is enabled by  
default. Will there be any problem if unicast is used?
- Thinking outside the box a bit more, besides the Tribe node usage, are  
there any recommended ES deployment architecture that satisfies my highly  
available and the single view of the data from two different data centers?

Thanks,  
Connie

--  
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/0a0e266b-718f-471d-b439-7beaeb02131a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0a0e266b-718f-471d-b439-7beaeb02131a%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, 12:54am UTC](https://discuss.elastic.co/t/elasticsearch-deployment-architecture-with-tribe-nodes/20392/2 "2017-07-06T00:54:19Z")

</div>