Martijn van Groningen c916c5e35b watcher: If during startup a watch record couldn't be saved because of a version conflict then overwrite it.
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
2015-11-10 09:24:15 +07:00
2015-11-05 10:39:28 -05:00
2015-10-30 11:16:29 -06:00
2018-04-20 14:16:58 -07:00
2015-11-04 11:19:13 -08:00

= Elasticsearch X Plugins

A set of Elastic's commercial plugins:

- License
- Shield
- Watcher
- Marvel

= Testing with Elasticsearch
Sometimes it is useful to use your local elasticsearch checkout with x-plugins. To do this, run the following commands:
cd buildSrc
gradle attach --name elasticsearch --path /path/to/elasticsearch/buildSrc
cd ..
gradle attach --name elasticsearch --path /path/to/elasticsearch

This will cause building x-plugins to reflect any changes in your elasticsearch repo. For example, if you make a change to elasticsearch core, building x-plugins will first re-build elasticsearch core, and use that when building x-plugins.

Description
🔎 Open source distributed and RESTful search engine.
Readme 546 MiB
Languages
Java 99.5%
Groovy 0.4%