# Thread\_pool \[management\]

**URL:** https://discuss.elastic.co/t/thread-pool-management/98628
**Category:** Elasticsearch
**Created:** [August 29, 2017, 5:33am UTC](https://discuss.elastic.co/t/thread-pool-management/98628 "2017-08-29T05:33:21Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![nestorbolivar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nestorbolivar/32/21603_2.png) [@nestorbolivar](https://discuss.elastic.co/u/nestorbolivar)
#### Post date: [August 29, 2017, 5:33am UTC](https://discuss.elastic.co/t/thread-pool-management/98628/1 "2017-08-29T05:33:21Z")

</div>

Could anyone explain what this thread does?! It seems that only this thread is consuming the most resources on my cluster yet I can't find how to tune it.

---

<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: [August 29, 2017, 8:00am UTC](https://discuss.elastic.co/t/thread-pool-management/98628/2 "2017-08-29T08:00:43Z")

</div>

What version are you on?

---

<div class="post-metadata">

### Author: ![nestorbolivar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nestorbolivar/32/21603_2.png) [@nestorbolivar](https://discuss.elastic.co/u/nestorbolivar)
#### Post date: [August 29, 2017, 8:15am UTC](https://discuss.elastic.co/t/thread-pool-management/98628/3 "2017-08-29T08:15:09Z")

</div>

Hi mate,

5.5 Docker image - saw somewhere there was a bug in a previous version related to this thread\_pool but i'm using the current stable.

Cheers

---

<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: [August 29, 2017, 8:19am UTC](https://discuss.elastic.co/t/thread-pool-management/98628/4 "2017-08-29T08:19:01Z")

</div>

Can you show the output from `_cat/threadpool`?

---

<div class="post-metadata">

### Author: ![nestorbolivar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nestorbolivar/32/21603_2.png) [@nestorbolivar](https://discuss.elastic.co/u/nestorbolivar)
#### Post date: [August 29, 2017, 8:36am UTC](https://discuss.elastic.co/t/thread-pool-management/98628/6 "2017-08-29T08:36:04Z")

</div>

Will do mate @warkolm . Not useful now as I'm recovering the cluster.

In general all the values are in 0 the only one that increases is management with a max value of 5. the search thread increases as well when searching something - part of the config file

```
thread_pool:
  search:
size: 40
queue_size: 10000
  bulk:
size: 2
queue_size: 300
  index:
size: 2
queue_size: 200
  warmer:
core: 1
max: 3
keep_alive: 5m

```

I'm disabling X-Pack module as the issue was introduced when upgrading from 2.4 to 5.5 (both on Docker and docker includes X-Pack)

```
xpack:
  monitoring:
    enabled: false
    exporters:
      my_local:
        type: local
  security:
    enabled: false
  ml:
    enabled: false
  graph:
    enabled: false
  watcher:
    enabled: false
    index:
      rest:
        direct_access: true

```

This is only a shot to see if it works... Takes a while to recover the cluster, I'll upload more info in a few hours.  
Cheers

---

<div class="post-metadata">

### Author: ![nestorbolivar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nestorbolivar/32/21603_2.png) [@nestorbolivar](https://discuss.elastic.co/u/nestorbolivar)
#### Post date: [August 29, 2017, 8:47am UTC](https://discuss.elastic.co/t/thread-pool-management/98628/7 "2017-08-29T08:47:59Z")

</div>

At this stage my cluster my cluster is with routing allocation: none

`"cluster.routing.allocation.enable": "none"`

And I can see this output - the other values are on 0

```
[root@prd-log-dnode-1-6 ~]$ curl -sL -XGET 'localhost:9200/_cat/thread_pool?v'|egrep management|sort
es-prd-log-knode-1-7 management 1 0 0
es-prd-log-knode-2-7 management 2 0 0
es-prd-log-knode-3-7 management 1 0 0
prd-log-dnode-1-6 management 1 0 0
prd-log-dnode-2-6 management 1 0 0
prd-log-dnode-3-6 management 1 0 0
prd-log-node-1-5 management 1 0 0
prd-log-node-2-5 management 1 0 0
prd-log-node-3-5 management 2 0 0

```

Cheers

---

<div class="post-metadata">

### Author: ![nestorbolivar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nestorbolivar/32/21603_2.png) [@nestorbolivar](https://discuss.elastic.co/u/nestorbolivar)
#### Post date: [September 5, 2017, 9:38am UTC](https://discuss.elastic.co/t/thread-pool-management/98628/8 "2017-09-05T09:38:30Z")

</div>

Thread [management] was consuming high percentage of resources on data nodes. The issue seems to disappear when migrating data nodes file systems from LVM-xfs to plain file system (ext4).

```
Infrastructure: ES running on AWS. 
Instance type: i3.2xlarge instances with NVME disks. 
DB size: 2.4TB across 3 data nodes. 
Docker version 17.05.0-ce, build 89658be
ES version: FROM docker.elastic.co/elasticsearch/elasticsearch:5.5.1
KV Store: Consul v0.8.5 
OS: CentOS Linux release 7.3.1611
```

---

<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: [October 3, 2017, 9:38am UTC](https://discuss.elastic.co/t/thread-pool-management/98628/9 "2017-10-03T09:38:37Z")

</div>

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