# Elasticsearch Watcher Stops processing after recovering from full disk **URL:** \ **Category:** Elasticsearch\ **Created:** [September 5, 2018, 4:18am UTC](https://discuss.elastic.co/t/elasticsearch-watcher-stops-processing-after-recovering-from-full-disk/147298 "2018-09-05T04:18:29Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![planetvortex](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/planetvortex/32/31080_2.png) [@planetvortex](https://discuss.elastic.co/u/planetvortex)\ **Post date:** [September 5, 2018, 4:18am UTC](https://discuss.elastic.co/t/elasticsearch-watcher-stops-processing-after-recovering-from-full-disk/147298/1 "2018-09-05T04:18:29Z")
3 times now I've managed to fill up my disks and after recovering the watcher service fails to work reliably. I end up having to restart each data node then it works fine. This isn't just my watches, but the system watches as well. I've tried stopping the service with POST \_xpack/watcher/\_stop followed by a start POST \_xpack/watcher/\_start it starts erroring right away on the console. [2018-09-04T22:55:07,503][WARN][o.e.x.w.e.ExecutionService] [myhost] failed to execute watch [322e52YFQ16I7v2vd9B8kQ\_logstash\_version\_mismatch] I've not seen any reason for it. This was just one example. ---
**Author:** ![planetvortex](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/planetvortex/32/31080_2.png) [@planetvortex](https://discuss.elastic.co/u/planetvortex)\ **Post date:** [September 5, 2018, 4:35am UTC](https://discuss.elastic.co/t/elasticsearch-watcher-stops-processing-after-recovering-from-full-disk/147298/2 "2018-09-05T04:35:24Z")
This can be deleted, ---
**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, 2018, 4:35am UTC](https://discuss.elastic.co/t/elasticsearch-watcher-stops-processing-after-recovering-from-full-disk/147298/3 "2018-10-03T04:35:24Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.