# Collector timeouts and high CPU utilization after installing X-Pack

**URL:** <https://discuss.elastic.co/t/collector-timeouts-and-high-cpu-utilization-after-installing-x-pack/108678>\
**Category:** Elasticsearch\
**Created:** [November 22, 2017, 9:12am UTC](https://discuss.elastic.co/t/collector-timeouts-and-high-cpu-utilization-after-installing-x-pack/108678 "2017-11-22T09:12:52Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbsj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mbsj/32/24378_2.png) [@mbsj](https://discuss.elastic.co/u/mbsj)\
**Post date:** [November 22, 2017, 9:12am UTC](https://discuss.elastic.co/t/collector-timeouts-and-high-cpu-utilization-after-installing-x-pack/108678/1 "2017-11-22T09:12:52Z")

</div>

I have installed X-Pack to Kibana, LogStash and Elasticsearch and generally it working fine (all version 6.0). However, i do have some issues in elasticseach.

When looking in the logs i get a lot of these errors:

```
[2017-11-22T09:59:49,403][ERROR][o.e.x.m.c.i.IndexStatsCollector] [COOPMSV2001] collector [index-stats] timed out when collecting data
[2017-11-22T09:59:59,418][ERROR][o.e.x.m.c.n.NodeStatsCollector] [COOPMSV2001] collector [node_stats] timed out when collecting data
[2017-11-22T10:00:09,434][ERROR][o.e.x.m.c.c.ClusterStatsCollector] [COOPMSV2001] collector [cluster_stats] timed out when collecting data

```

Also, when looking at CPU utilization, elasticsearch has a contant high CPU load of 25-50%. This occurs with LogStash and Kibana stopped and no other activity on the server; basically idling.

I have a single node running both elasticsearch and logstash and another node running kibana.

---

<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:** [November 22, 2017, 9:13am UTC](https://discuss.elastic.co/t/collector-timeouts-and-high-cpu-utilization-after-installing-x-pack/108678/2 "2017-11-22T09:13:43Z")

</div>

I moved this to X-Pack, cause the Elasticsearch team that works on it hangs out in there 🙂

---

<div class="post-metadata">

**Author:** ![mbsj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mbsj/32/24378_2.png) [@mbsj](https://discuss.elastic.co/u/mbsj)\
**Post date:** [November 22, 2017, 9:14am UTC](https://discuss.elastic.co/t/collector-timeouts-and-high-cpu-utilization-after-installing-x-pack/108678/3 "2017-11-22T09:14:28Z")

</div>

Thank you @warkolm 😄

---

<div class="post-metadata">

**Author:** ![mbsj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mbsj/32/24378_2.png) [@mbsj](https://discuss.elastic.co/u/mbsj)\
**Post date:** [November 24, 2017, 6:37am UTC](https://discuss.elastic.co/t/collector-timeouts-and-high-cpu-utilization-after-installing-x-pack/108678/4 "2017-11-24T06:37:24Z")

</div>

No updates on this? Right now monitoring is disabled and it would be nice to be able to enable it again.

---

<div class="post-metadata">

**Author:** ![mbsj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mbsj/32/24378_2.png) [@mbsj](https://discuss.elastic.co/u/mbsj)\
**Post date:** [November 28, 2017, 9:28am UTC](https://discuss.elastic.co/t/collector-timeouts-and-high-cpu-utilization-after-installing-x-pack/108678/5 "2017-11-28T09:28:56Z")

</div>

I'll pump this one more time. Can it really be that no one has any input or suggestions?

---

<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:** [December 26, 2017, 9:29am UTC](https://discuss.elastic.co/t/collector-timeouts-and-high-cpu-utilization-after-installing-x-pack/108678/6 "2017-12-26T09:29:20Z")

</div>

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