# Known tribe bug for ES v1.7.1?

**URL:** <https://discuss.elastic.co/t/known-tribe-bug-for-es-v1-7-1/29077>\
**Category:** Elasticsearch\
**Created:** [September 10, 2015, 10:22pm UTC](https://discuss.elastic.co/t/known-tribe-bug-for-es-v1-7-1/29077 "2015-09-10T22:22:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![tinle](https://avatars.discourse-cdn.com/v4/letter/t/c77e96/32.png) [@tinle](https://discuss.elastic.co/u/tinle)\
**Post date:** [September 10, 2015, 10:22pm UTC](https://discuss.elastic.co/t/known-tribe-bug-for-es-v1-7-1/29077/1 "2015-09-10T22:22:22Z")

</div>

I've been testing ES v1.7.1 before upgrading all our clusters, and noticed a pretty serious bug when using it as tribe.

We are using tribe nodes to aggregate many downstream clusters. Over 90 clusters, 14K indices. Using v1.4.5 tribe node, I can see all downstream nodes and indices. Tested upgrading to 1.7.1 and it see only around 30% of downstream nodes, which also mean many indices are missing.

This is a major bug that is keeping us from upgrading. I've filed a bug with Elastic, just wanted to know if anyone else had similar experience.

---

<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:** [September 11, 2015, 1:13am UTC](https://discuss.elastic.co/t/known-tribe-bug-for-es-v1-7-1/29077/2 "2015-09-11T01:13:49Z")

</div>

Which issue is the one you raised on GH?

---

<div class="post-metadata">

**Author:** ![tinle](https://avatars.discourse-cdn.com/v4/letter/t/c77e96/32.png) [@tinle](https://discuss.elastic.co/u/tinle)\
**Post date:** [September 11, 2015, 1:15am UTC](https://discuss.elastic.co/t/known-tribe-bug-for-es-v1-7-1/29077/3 "2015-09-11T01:15:53Z")

</div>

Through Elastic support site since I have paid support. I could open a github ticket too if that helps to track the problem. It's reproduceable for me.

---

<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:** [September 11, 2015, 1:16am UTC](https://discuss.elastic.co/t/known-tribe-bug-for-es-v1-7-1/29077/4 "2015-09-11T01:16:53Z")

</div>

Ahh ok, that's probably the best option then 🙂

However I haven't seen this, but then I haven't seen a great deal of tribe deployments myself.

---

<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 5, 2017, 11:51pm UTC](https://discuss.elastic.co/t/known-tribe-bug-for-es-v1-7-1/29077/5 "2017-07-05T23:51:01Z")

</div>