# Collector \[index\_recovery\] timed out when collecting data

**URL:** <https://discuss.elastic.co/t/collector-index-recovery-timed-out-when-collecting-data/166821>\
**Category:** Elasticsearch\
**Created:** [February 2, 2019, 1:26pm UTC](https://discuss.elastic.co/t/collector-index-recovery-timed-out-when-collecting-data/166821 "2019-02-02T13:26:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vnallamothu](https://avatars.discourse-cdn.com/v4/letter/v/35a633/32.png) [@vnallamothu](https://discuss.elastic.co/u/vnallamothu)\
**Post date:** [February 2, 2019, 1:26pm UTC](https://discuss.elastic.co/t/collector-index-recovery-timed-out-when-collecting-data/166821/1 "2019-02-02T13:26:12Z")

</div>

Recently, we started to see this error in the logs of master nodes. After a series of this error messages, the cluster will remove one of the problematic data nodes. Thereafter automatically, it is adding the data node back.

This process is repeating on a regular interval. On the problematic data node, I found following logs:

`[2019-02-02T03:48:15,082][WARN][o.e.m.j.JvmGcMonitorService] [es6-data-04] [gc][3019] overhead, spent [640ms] collecting in the last [1s]`

Can anyone assist me regarding this?

---

<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:** [March 2, 2019, 1:26pm UTC](https://discuss.elastic.co/t/collector-index-recovery-timed-out-when-collecting-data/166821/2 "2019-03-02T13:26:26Z")

</div>

Closed on March 2, 2019, 1:26pm UTC

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