# Elasticsearch 2.4.3 very high cpu usage

**URL:** <https://discuss.elastic.co/t/elasticsearch-2-4-3-very-high-cpu-usage/184424>\
**Category:** Elasticsearch\
**Created:** [June 5, 2019, 5:00pm UTC](https://discuss.elastic.co/t/elasticsearch-2-4-3-very-high-cpu-usage/184424 "2019-06-05T17:00:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 5, 2019, 5:15pm UTC](https://discuss.elastic.co/t/elasticsearch-2-4-3-very-high-cpu-usage/184424/2 "2019-06-05T17:15:04Z")

</div>

What is the output of:

```auto
GET /
GET /_cat/nodes?v
GET /_cat/health?v
GET /_cat/indices?v
# Optionally 
GET /_cat/shards?v

```

If some outputs are too big, please share them on [gist.github.com](http://gist.github.com) and link them here.

Please format your code, logs or configuration files using `</>` icon as explained in [this guide](https://discuss.elastic.co/t/about-the-elasticsearch-category/21) and not the citation button. It will make your post more readable.

Or use markdown style like:

````
```
CODE
```

````

This is the icon to use if you are not using markdown format:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/e/7e6e239431ec2d71cbf1beef741f2e93e7cc762c.jpg)

There's a live preview panel for exactly this reasons.

Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-2-4-3-very-high-cpu-usage/184424)._