# Many active indices:admin/get tasks

**URL:** https://discuss.elastic.co/t/many-active-indices-admin-get-tasks/87225
**Category:** Elasticsearch
**Created:** [May 26, 2017, 9:59am UTC](https://discuss.elastic.co/t/many-active-indices-admin-get-tasks/87225 "2017-05-26T09:59:55Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![dwjvaughan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dwjvaughan/32/10648_2.png) [@dwjvaughan](https://discuss.elastic.co/u/dwjvaughan)
#### Post date: [May 26, 2017, 9:59am UTC](https://discuss.elastic.co/t/many-active-indices-admin-get-tasks/87225/1 "2017-05-26T09:59:55Z")

</div>

Hi all,

Have a strange issue where we have around 1500 active tasks on our 5 node 5.2 ES cluster. They are all on the same node (current master, and endpoint for Kibana/Monitoring) and go back for days.

Any ideas what these could be? I tried to do a bulk cancel on them to no avail.

`curl "http://<server>:9200/_cat/tasks?v&h=action,task_id,parent_task_id,type,timestamp"`  
...  
`indices:admin/get I_eYf5eiTX-uwkuoO2huEA:26400939 - transport 09:58:17`  
...

I'm not sure if it's causing an issue, but it's not happening on our 2.3 cluster.

Any help greatly appreciated!

Dave

---

<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: [May 26, 2017, 10:02am UTC](https://discuss.elastic.co/t/many-active-indices-admin-get-tasks/87225/2 "2017-05-26T10:02:24Z")

</div>

Do you have a transport client connected to the cluster?

---

<div class="post-metadata">

### Author: ![dwjvaughan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dwjvaughan/32/10648_2.png) [@dwjvaughan](https://discuss.elastic.co/u/dwjvaughan)
#### Post date: [May 26, 2017, 10:04am UTC](https://discuss.elastic.co/t/many-active-indices-admin-get-tasks/87225/3 "2017-05-26T10:04:11Z")

</div>

Not quite sure what would constitute as a transport client. We do use the readonlyrest plugin though, although that's on all nodes in the cluster, not just the master (where I'm seeing this).

---

<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: [May 26, 2017, 10:09am UTC](https://discuss.elastic.co/t/many-active-indices-admin-get-tasks/87225/4 "2017-05-26T10:09:12Z")

</div>

What does `_cat/nodes` show?

---

<div class="post-metadata">

### Author: ![dwjvaughan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dwjvaughan/32/10648_2.png) [@dwjvaughan](https://discuss.elastic.co/u/dwjvaughan)
#### Post date: [May 26, 2017, 10:12am UTC](https://discuss.elastic.co/t/many-active-indices-admin-get-tasks/87225/5 "2017-05-26T10:12:03Z")

</div>

```
ip heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name
172.16.16.56 21 97 0 0.01 0.03 0.05 mdi - nodeb
172.16.16.46 27 98 0 0.00 0.01 0.05 mdi - noded
172.16.16.73 74 98 0 0.00 0.01 0.05 mdi - nodee
172.16.16.13 43 98 0 0.00 0.01 0.05 mdi - nodec
172.16.16.23 24 98 1 0.03 0.04 0.05 mdi * nodea

```

One other thing I've noticed with the tasks - they appear to be every minute, and there are 4 of them for each minute.

---

<div class="post-metadata">

### Author: ![dwjvaughan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dwjvaughan/32/10648_2.png) [@dwjvaughan](https://discuss.elastic.co/u/dwjvaughan)
#### Post date: [May 26, 2017, 1:53pm UTC](https://discuss.elastic.co/t/many-active-indices-admin-get-tasks/87225/6 "2017-05-26T13:53:14Z")

</div>

I've just check, this is actually happening on our single-node 5.3.2 instance too. Any ideas what might be doing it?

---

<div class="post-metadata">

### Author: ![dwjvaughan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dwjvaughan/32/10648_2.png) [@dwjvaughan](https://discuss.elastic.co/u/dwjvaughan)
#### Post date: [May 31, 2017, 2:03pm UTC](https://discuss.elastic.co/t/many-active-indices-admin-get-tasks/87225/7 "2017-05-31T14:03:27Z")

</div>

I've done a bit more digging on this - it appears to be related to http auth, readonlyrest and Sense. When you are prompted for user/password it's logged as a failed attempt in the ROR logs, but the `indices:admin/get` task hangs around.

I've [raised it to readonlyrest](https://github.com/sscarduzio/elasticsearch-readonlyrest-plugin/issues/236) but I'm not sure if this is an ES bug or ROR - the problem is I can't cancel the tasks in ES.

---

<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: [June 28, 2017, 2:03pm UTC](https://discuss.elastic.co/t/many-active-indices-admin-get-tasks/87225/8 "2017-06-28T14:03:31Z")

</div>

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