c916c5e35b
In certain cases this could cause Watcher to prevent from being started (either automatically or manually): * The watch of the triggered watch doesn't exist * The execution service rejected the execution the watch. (due to not enough threads in the thread pool) If a watch record gets overwritten this means it has been executed before when watcher was running, but we were unable to delete the triggered watch. So we executed the a watch twice with the same trigger event. This can happen if watcher was stopped before because of the node running Watcher unexpectedly stopped (master left, power loss etc.) In stead of failing to write the watch record, we overwrite it set the state 'executed_multiple_times'. Closes elastic/elasticsearch#695 Original commit: elastic/x-pack-elasticsearch@20f805cb99 |
||
|---|---|---|
| .. | ||
| bin/watcher | ||
| dev-tools | ||
| docs | ||
| src | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| README.asciidoc | ||
| build.gradle | ||
README.asciidoc
= Elasticsearch Watcher Plugin This plugins adds conditioned scheduled tasks features to elasticsearch - such a task is called a `Watch`. You can build the plugin with `mvn package`. The documentation is put in the `docs/` directory.