# Pending tasks list flooded with \_add\_listener\_ tasks

**URL:** <https://discuss.elastic.co/t/pending-tasks-list-flooded-with--add-listener--tasks/44636>\
**Category:** Elasticsearch\
**Created:** [March 16, 2016, 11:29pm UTC](https://discuss.elastic.co/t/pending-tasks-list-flooded-with--add-listener--tasks/44636 "2016-03-16T23:29:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![roper](https://avatars.discourse-cdn.com/v4/letter/r/ac91a4/32.png) [@roper](https://discuss.elastic.co/u/roper)\
**Post date:** [March 16, 2016, 11:29pm UTC](https://discuss.elastic.co/t/pending-tasks-list-flooded-with--add-listener--tasks/44636/1 "2016-03-16T23:29:19Z")

</div>

I have an elasticsearch cluster running with a handful of nodes and it periodically (as in every few minutes) falls down with a master\_not\_discovered\_exception. While investigating I notice that when I check \_cat/pending\_tasks there are hundreds of pending tasks with source == "_add\_listener_".

Example:  
`672140 387ms HIGH _add_listener_`

I'm trying to find out what kind of requests result in an _add\_listener_ task so that I can track down the source of the requests. Any help would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [March 18, 2016, 3:22pm UTC](https://discuss.elastic.co/t/pending-tasks-list-flooded-with--add-listener--tasks/44636/2 "2016-03-18T15:22:47Z")

</div>

I don't know that code very well but I do know that you'll need to tell us what version of Elasticsearch you are using for anyone to be able to help.

---

<div class="post-metadata">

**Author:** ![roper](https://avatars.discourse-cdn.com/v4/letter/r/ac91a4/32.png) [@roper](https://discuss.elastic.co/u/roper)\
**Post date:** [March 22, 2016, 8:19pm UTC](https://discuss.elastic.co/t/pending-tasks-list-flooded-with--add-listener--tasks/44636/3 "2016-03-22T20:19:37Z")

</div>

We are running 2.2.0, on Windows Server 2012 R2. There are 11 nodes in the cluster. They are all master and data nodes. Right now I'm not actively indexing any documents but there are about 120,000 documents already indexed.

It seems like long queue times are causing the ping requests to timeout, but I'm not sure why the pending tasks queue is long when I'm not indexing or querying anything.

---

<div class="post-metadata">

**Author:** ![awislowski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/awislowski/32/3789_2.png) [@awislowski](https://discuss.elastic.co/u/awislowski)\
**Post date:** [April 28, 2016, 12:37pm UTC](https://discuss.elastic.co/t/pending-tasks-list-flooded-with--add-listener--tasks/44636/4 "2016-04-28T12:37:14Z")

</div>

Hi Robert, have solved this problem on Mac.

For version 2.2.1 I have similar entries with kibana connection errors to elasticsearch frequently.

---

<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:** [July 5, 2017, 10:55pm UTC](https://discuss.elastic.co/t/pending-tasks-list-flooded-with--add-listener--tasks/44636/5 "2017-07-05T22:55:34Z")

</div>