Force watcher execution by node id

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.

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 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

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