# Tribe node crash: full of old stats **URL:** \ **Category:** Elasticsearch\ **Created:** [March 5, 2018, 3:36pm UTC](https://discuss.elastic.co/t/tribe-node-crash-full-of-old-stats/122557 "2018-03-05T15:36:32Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ebillaud](https://avatars.discourse-cdn.com/v4/letter/e/f475e1/32.png) [@ebillaud](https://discuss.elastic.co/u/ebillaud)\ **Post date:** [March 5, 2018, 3:36pm UTC](https://discuss.elastic.co/t/tribe-node-crash-full-of-old-stats/122557/1 "2018-03-05T15:36:32Z")
Hello, We have our Tribe node (v5.3.0) that crashed recently. The hprof analysis showed that it was full of old statistics. It is connected to 3 clusters. For two of them, there were statistics 10 minutes old. In the following images, the retained size is the size for a single NodeStats object (for a given IP, and a given timestamp). Cluster 1 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/6/16ce703db1aabc0a36a00f8f23b6b12b45b386e9.png) Cluster 2 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/b/cb971e79f1e22ba6e8319f47c32767b8e25cb607.png) Here is the path to GC roots for one of those 10 minutes old NodeStats: ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/f/9fb319516c629617647ece383a178d3bed167e2e.png) Is having old statistics an expected behavior ? Are there any tribe specific configuration to prevent from keeping them for more than few minutes (1 or 2) ? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 2, 2018, 3:36pm UTC](https://discuss.elastic.co/t/tribe-node-crash-full-of-old-stats/122557/2 "2018-04-02T15:36:42Z")
Closed on April 2, 2018, 3:36pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.