# Generic scheduling

**URL:** <https://discuss.elastic.co/t/generic-scheduling/1000>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-alerting\
**Created:** [May 20, 2015, 4:57pm UTC](https://discuss.elastic.co/t/generic-scheduling/1000 "2015-05-20T16:57:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jbaranick](https://avatars.discourse-cdn.com/v4/letter/j/977dab/32.png) [@jbaranick](https://discuss.elastic.co/u/jbaranick)\
**Post date:** [May 20, 2015, 4:57pm UTC](https://discuss.elastic.co/t/generic-scheduling/1000/1 "2015-05-20T16:57:20Z")

</div>

Have you considered using the scheduling portion of Watcher for more generic purposes? For example, Curator could be built as a plugin to Elasticsearch and use the scheduling portion of watcher for cluster maintenance.

---

<div class="post-metadata">

**Author:** ![mvg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mvg/32/98890_2.png) [@mvg](https://discuss.elastic.co/u/mvg)\
**Post date:** [May 20, 2015, 8:49pm UTC](https://discuss.elastic.co/t/generic-scheduling/1000/2 "2015-05-20T20:49:12Z")

</div>

That idea did come up during development of Watcher. It is being tracked here: [https://github.com/elastic/elasticsearch/issues/6914](https://github.com/elastic/elasticsearch/issues/6914)

---

<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:** [July 6, 2017, 1:50pm UTC](https://discuss.elastic.co/t/generic-scheduling/1000/3 "2017-07-06T13:50:03Z")

</div>