# Tribe nodes in ES 2.2.0 breaks plugins

**URL:** <https://discuss.elastic.co/t/tribe-nodes-in-es-2-2-0-breaks-plugins/43312>\
**Category:** Elasticsearch\
**Created:** [March 2, 2016, 9:48pm UTC](https://discuss.elastic.co/t/tribe-nodes-in-es-2-2-0-breaks-plugins/43312 "2016-03-02T21:48:50Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![thn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thn/32/8061_2.png) [@thn](https://discuss.elastic.co/u/thn)\
**Post date:** [March 3, 2016, 10:53am UTC](https://discuss.elastic.co/t/tribe-nodes-in-es-2-2-0-breaks-plugins/43312/3 "2016-03-03T10:53:24Z")

</div>

Unless you use the build that has the fix for the reported github reference, I think you'll still need to put in the path.\* for plugins, even though it's been said "you dont have to".

When you have kibana and/or marvel running with the tribe node setup, on startup, kibana does not know which cluster it should create .kibana (default) index. The link to a post below has a reference link describing what could be done.

> [@Query multiple ES nodes from single Kibana instance](https://discuss.elastic.co/t/query-multiple-es-nodes-from-single-kibana-instance/42071/10):
>
> Given that you can use tribe nodes, will the search latency acceptable when one ES node has to go to 10+ ES instances separated geographically to get data? Do you need to search data from 10+ nodes in real time? If not I still prefer using something to slowly ship data from 10+ nodes to a central ES node where we can do whatever we want at high speed. It would be easier than having to maintain separate ES nodes.

The new version of marvel needs kibana and it needs to create .marvel- indices. The same issue here, it needs to know which cluster it should drop the daily index. I think by creating or using a separate "monitoring cluster", following the instructions at the link below, the marvel issue can be solved. I've not done this but I think it will help addressing the issue.

> **[Installing Marvel | Marvel Documentation \[2.4\] | Elastic](https://www.elastic.co/guide/en/marvel/current/installing-marvel.html)**

---

_[View the full topic](https://discuss.elastic.co/t/tribe-nodes-in-es-2-2-0-breaks-plugins/43312)._
