# Force watcher execution by node id
**URL:** https://discuss.elastic.co/t/force-watcher-execution-by-node-id/126604
**Category:** Elasticsearch
**Tags:** elastic-stack-alerting
**Created:** [April 3, 2018, 4:08pm UTC](https://discuss.elastic.co/t/force-watcher-execution-by-node-id/126604 "2018-04-03T16:08:11Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@None123455555](https://discuss.elastic.co/u/None123455555)
#### Post date: [April 3, 2018, 4:08pm UTC](https://discuss.elastic.co/t/force-watcher-execution-by-node-id/126604/1 "2018-04-03T16:08:12Z")
Is it possible to force a watcher to run on a specific node? My watcher consumes quite some memory. I don't want it to use the master node as to my experience the cluster does not easily recover when too much memory is allocated.
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [April 4, 2018, 7:27am UTC](https://discuss.elastic.co/t/force-watcher-execution-by-node-id/126604/2 "2018-04-04T07:27:58Z")
It depends which major version you are using. If you are running on 5.x, then all watches get executed on the current master node.
If you happen to run on 6.x, then the watches are executed where the shards are. So if you use [shard allocation filtering](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/shard-allocation-filtering.html) you can watches on dedicated nodes only.
See also [https://www.elastic.co/guide/en/x-pack/6.2/how-watcher-works.html#watch-execution](https://www.elastic.co/guide/en/x-pack/6.2/how-watcher-works.html#watch-execution)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 2, 2018, 7:28am UTC](https://discuss.elastic.co/t/force-watcher-execution-by-node-id/126604/3 "2018-05-02T07:28:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.