# High query/indexing time one node (cpu ok)

**URL:** <https://discuss.elastic.co/t/high-query-indexing-time-one-node-cpu-ok/215907>\
**Category:** Elasticsearch\
**Created:** [January 21, 2020, 3:32pm UTC](https://discuss.elastic.co/t/high-query-indexing-time-one-node-cpu-ok/215907 "2020-01-21T15:32:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bruno\_z](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bruno_z/32/61143_2.png) [@bruno\_z](https://discuss.elastic.co/u/bruno_z)\
**Post date:** [January 21, 2020, 3:32pm UTC](https://discuss.elastic.co/t/high-query-indexing-time-one-node-cpu-ok/215907/1 "2020-01-21T15:32:21Z")

</div>

I'm facing high query/indexing time for just one node.

- My cluster has 8 nodes
- My index has 5 primary shards and 3 replicas

I checked the shards using the **\_cat/shards** api, and everything looks as expected.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/e/9ea9c8e59741230a13abc489ab6ebe3780777cc1.png)

The cpu is ok.

I already tried rebooting the node, but it just moves the problem to another one.

Any idea?

* * *

Elasticsearch version: 5.5.1

---

<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:** [February 18, 2020, 3:32pm UTC](https://discuss.elastic.co/t/high-query-indexing-time-one-node-cpu-ok/215907/2 "2020-02-18T15:32:22Z")

</div>

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