Adrien Grand c633b919ab Watcher's ExecutionService is not thread-safe. (elastic/x-pack-elasticsearch#3861) ... If start, stop and/or clearExecutions are called concurrently, you could end up in an inconsistent state where `currentExecutions.sealAndAwaitEmpty` is called twice on the same instance. These `synchronized` keywords should make it a bit better, though I suspect there are other issues and thread safety of this class should be reviewed. This might have caused https://internal-ci.elastic.co/job/elastic+x-pack-elasticsearch+5.6+multijob-unix-compatibility/932/consoleFull Original commit: elastic/x-pack-elasticsearch@2f7e7a34d9		2018-02-13 11:27:11 +01:00
..
licenses	More license file corrections	2018-01-18 16:34:25 -08:00
src	Watcher's ExecutionService is not thread-safe. (elastic/x-pack-elasticsearch#3861)	2018-02-13 11:27:11 +01:00
build.gradle	Build: Replace provided configuration with compileOnly (elastic/x-pack-elasticsearch#3868)	2018-02-09 11:30:43 -08:00