# Cross Cluster Search vs Tribe Node

**URL:** <https://discuss.elastic.co/t/cross-cluster-search-vs-tribe-node/80633>\
**Category:** Elasticsearch\
**Created:** [March 30, 2017, 8:53am UTC](https://discuss.elastic.co/t/cross-cluster-search-vs-tribe-node/80633 "2017-03-30T08:53:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![anshulagrawal](https://avatars.discourse-cdn.com/v4/letter/a/c89c15/32.png) [@anshulagrawal](https://discuss.elastic.co/u/anshulagrawal)\
**Post date:** [March 30, 2017, 8:53am UTC](https://discuss.elastic.co/t/cross-cluster-search-vs-tribe-node/80633/1 "2017-03-30T08:53:30Z")

</div>

In 5.3.0 version, a new capability of cluster search is being provided and this [link](https://www.elastic.co/blog/elasticsearch-5-3-0-released?ultron=mar-2017&blade=newsletter&hulk=email&mkt_tok=eyJpIjoiTkRneU5tSTRaalZtWVRnMiIsInQiOiJTdlpnc3o0MUhNZUpVcW5qa3hxNVp6ZmlHalFjRTYydDRsNWpxZnhmYXROczJmTFducTJOOXBZWCt2NDVtbUVpcml1Q29ucWJZOVgrZlh5SkZrK1lOaDJyeDV5elB6aDBqM0R1WlJvMVd2K2lRVUV6SzZVTFVleGk1M0xKVDJBQyJ9) says cross cluster search has solved many of these problems . But cross cluster serach is in experimental mode and the warning says this may be removed in future versions. I wanted help with the following here : 1) Is there a list of the issues that are present in tribe node? 2) Is there a list of the issues present in cross cluster search?

Our cluster is around 40TB+ and we are planning to split it. For this split we are exploring approaches for cross cluster search.

---

<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:** [March 30, 2017, 8:57am UTC](https://discuss.elastic.co/t/cross-cluster-search-vs-tribe-node/80633/2 "2017-03-30T08:57:40Z")

</div>

> [@anshulagrawal](#):
>
> the warning says this may be removed in future versions

Yeah, we do that for every experimental feature, but we fully expect this to replace tribe. So while it may change a fair bit, I don't think it's going to be removed 🙂

For the issues, you'll have to check out github. eg [Issues · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3A%22%3ATribe%20Node%22%20)

---

<div class="post-metadata">

**Author:** ![anshulagrawal](https://avatars.discourse-cdn.com/v4/letter/a/c89c15/32.png) [@anshulagrawal](https://discuss.elastic.co/u/anshulagrawal)\
**Post date:** [March 30, 2017, 9:16am UTC](https://discuss.elastic.co/t/cross-cluster-search-vs-tribe-node/80633/3 "2017-03-30T09:16:45Z")

</div>

Thanks for the reply !

Is there any provision for managing writes also for multiple clusters? If not present now, any plans for providing this in future?

---

<div class="post-metadata">

**Author:** ![anshulagrawal](https://avatars.discourse-cdn.com/v4/letter/a/c89c15/32.png) [@anshulagrawal](https://discuss.elastic.co/u/anshulagrawal)\
**Post date:** [April 12, 2017, 10:38am UTC](https://discuss.elastic.co/t/cross-cluster-search-vs-tribe-node/80633/4 "2017-04-12T10:38:12Z")

</div>

HI,

Is there any label where we are tracking issues being faced in cross-cluster search?

---

<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:** [April 13, 2017, 3:37am UTC](https://discuss.elastic.co/t/cross-cluster-search-vs-tribe-node/80633/5 "2017-04-13T03:37:29Z")

</div>

From what I can see it's under the `:Search` label.

---

<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:** [May 11, 2017, 3:37am UTC](https://discuss.elastic.co/t/cross-cluster-search-vs-tribe-node/80633/6 "2017-05-11T03:37:42Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
