# Watchers cause master node load spike

**URL:** <https://discuss.elastic.co/t/watchers-cause-master-node-load-spike/94980>\
**Category:** Elasticsearch\
**Created:** [July 28, 2017, 3:01pm UTC](https://discuss.elastic.co/t/watchers-cause-master-node-load-spike/94980 "2017-07-28T15:01:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![amercado](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@amercado](https://discuss.elastic.co/u/amercado)\
**Post date:** [July 28, 2017, 3:01pm UTC](https://discuss.elastic.co/t/watchers-cause-master-node-load-spike/94980/1 "2017-07-28T15:01:26Z")

</div>

![elasticsearch-master-load](https://us1.discourse-cdn.com/elastic/original/3X/6/7/678ca41f3efd55c1872c256bfb1950292ee53f0a.png)

Notice the monitoring graph. There is a spike in load every 10 minutes which coincides with the interval time of our watchers (3 of them). Why are these causing such high load on the master? Since the data node in our 2 node setup will handle the grunt of the "work" for searches and the master is doing relatively little work, why would this happen for watchers? Should I expect the same behavior if I force the data node to execute watchers instead of the master?

---

<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:** [August 25, 2017, 3:02pm UTC](https://discuss.elastic.co/t/watchers-cause-master-node-load-spike/94980/2 "2017-08-25T15:02:51Z")

</div>

Closed on August 25, 2017, 3:02pm UTC

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