# Scalability of Alerting
**URL:** https://discuss.elastic.co/t/scalability-of-alerting/214058
**Category:** Elasticsearch
**Tags:** elastic-stack-alerting
**Created:** [January 7, 2020, 1:08pm UTC](https://discuss.elastic.co/t/scalability-of-alerting/214058 "2020-01-07T13:08:15Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@krupniok](https://discuss.elastic.co/u/krupniok)
#### Post date: [January 7, 2020, 1:08pm UTC](https://discuss.elastic.co/t/scalability-of-alerting/214058/1 "2020-01-07T13:08:15Z")
Hi there!
I have a question regarding the alerting-feature. The official documentation states that if too many watches trigger concurrently and there isn’t enough capacity to execute them all, some of the watches are queued. Will it reduce the number of queued watches if i add another node to the cluster?
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [January 7, 2020, 4:47pm UTC](https://discuss.elastic.co/t/scalability-of-alerting/214058/2 "2020-01-07T16:47:12Z")
Yes, thanks to [distributed watch execution](https://www.elastic.co/blog/distributed-watch-execution-elasticsearch-6.0), as long as the new node has a shard (primary or replica) of the `.watches` index. You may need to add a replica to achieve this.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 4, 2020, 4:47pm UTC](https://discuss.elastic.co/t/scalability-of-alerting/214058/3 "2020-02-04T16:47:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.