# Tribe node to ignore cluster events **URL:** \ **Category:** Elasticsearch\ **Created:** [May 18, 2017, 7:38pm UTC](https://discuss.elastic.co/t/tribe-node-to-ignore-cluster-events/86328 "2017-05-18T19:38:50Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![bennett](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bennett/32/4903_2.png) [@bennett](https://discuss.elastic.co/u/bennett)\ **Post date:** [May 18, 2017, 7:38pm UTC](https://discuss.elastic.co/t/tribe-node-to-ignore-cluster-events/86328/1 "2017-05-18T19:38:51Z")
Hi, I have tribe nodes that look at multiple clusters, but every time there's a index rotation or any sort of maintenance, the tribe node goes down until things are allocated and back to normal which could take over an hour. I heard there was a patch that was given to blizzard for the tribe node to ignore cluster events. I was wondering if I could get a similar patch or tell me how to patch it? Thanks! Krystle ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [May 19, 2017, 2:34am UTC](https://discuss.elastic.co/t/tribe-node-to-ignore-cluster-events/86328/2 "2017-05-19T02:34:14Z")
> [@bennett](#): > > I heard there was a patch that was given to blizzard for the tribe node to ignore cluster events. Completely ignoring cluster "events" is inherently dangerous yet there are aspects of cluster state updates that are expensive yet can be ignored on tribe nodes. > [@bennett](#): > > I was wondering if I could get a similar patch or tell me how to patch it? Upgrade to a version that includes [Skip shard management code when updating cluster state on client/tribe nodes by ywelsch · Pull Request #20731 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/pull/20731) (first released in 2.4.2, and also included in 5.0.0). ---
**Author:** ![bennett](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bennett/32/4903_2.png) [@bennett](https://discuss.elastic.co/u/bennett)\ **Post date:** [May 19, 2017, 3:19pm UTC](https://discuss.elastic.co/t/tribe-node-to-ignore-cluster-events/86328/3 "2017-05-19T15:19:51Z")
I'm running version 2.4.4 . wouldn't that have the change if 2.4.2 has it? ---
**Author:** ![bennett](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bennett/32/4903_2.png) [@bennett](https://discuss.elastic.co/u/bennett)\ **Post date:** [May 19, 2017, 3:24pm UTC](https://discuss.elastic.co/t/tribe-node-to-ignore-cluster-events/86328/4 "2017-05-19T15:24:39Z")
What else could I do to for more stability for the tribe nodes? ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [May 19, 2017, 3:31pm UTC](https://discuss.elastic.co/t/tribe-node-to-ignore-cluster-events/86328/5 "2017-05-19T15:31:23Z")
Yes. ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [May 19, 2017, 3:31pm UTC](https://discuss.elastic.co/t/tribe-node-to-ignore-cluster-events/86328/6 "2017-05-19T15:31:53Z")
I don't know because I don't have enough detail to assess what your problem is. ---
**Author:** ![bennett](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bennett/32/4903_2.png) [@bennett](https://discuss.elastic.co/u/bennett)\ **Post date:** [May 19, 2017, 3:34pm UTC](https://discuss.elastic.co/t/tribe-node-to-ignore-cluster-events/86328/7 "2017-05-19T15:34:26Z")
basically when the indices rotate (create new ones and delete old ones), the tribe node goes in a red state saying it can't connect to elasticsearch. This happens for an hour sometimes as the clusters are trying to stabilize. We have users trying to access the tribe nodes but get errors. We are looking to reduce the downtime of the tribe node. And when I was listening to blizzard (which looks like we have a similar setup) they mentioned there was a patch that was applied that helped with the downtime of the tribe node. ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [May 20, 2017, 1:56pm UTC](https://discuss.elastic.co/t/tribe-node-to-ignore-cluster-events/86328/8 "2017-05-20T13:56:13Z")
> [@bennett](#): > > basically when the indices rotate (create new ones and delete old ones), the tribe node goes in a red state saying it can't connect to elasticsearch. Please provide logs. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 17, 2017, 1:56pm UTC](https://discuss.elastic.co/t/tribe-node-to-ignore-cluster-events/86328/9 "2017-06-17T13:56:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.