Alexander Reelsen 79a8f27569 Watcher: Remove WatchLockService (elastic/elasticsearch#4365) ...

The watch lock service is not really needed, as there is already
a data structure that has information about the currently executing
watches, that can be consulted before executed.

This change will now check, if there is already a watch running with
the current id. If there is not, execution will happen as usual. If
there is however, than a watch record will be created, stating that
the watch is currently being executed - which means that it is either
being executed or in the list of planned executions.

This way users can check in the watch history, if a watch has been executed
more often than it should.

In order to easily search for this, a new execution state called
`NOT_EXECUTED_ALREADY_QUEUED` has been added.

Original commit: elastic/x-pack-elasticsearch@867acec3c3

2016-12-19 17:33:48 +01:00

..

bin/x-pack

Build: Reorganize src roots

2016-10-01 09:46:43 +02:00

config/x-pack

Build: Reorganize src roots

2016-10-01 09:46:43 +02:00

keys

Collapsed license code into xpack src

2016-09-29 12:22:19 +02:00

src

Watcher: Remove WatchLockService (elastic/elasticsearch#4365)

2016-12-19 17:33:48 +01:00

build.gradle

Build: Convert xplugins to use new extra projects setup (elastic/elasticsearch#4175)

2016-12-14 15:02:28 -08:00

NOTICE.txt

Moved directories around

2016-09-29 12:03:14 +02:00