🔎 Open source distributed and RESTful search engine.

Martijn van Groningen 66a2f999e5 scheduler: prevent stopping scheduler before the scheduler was actually started ... The start scheduler waits until the scheduler state has been set to started before returning. Before this change after the scheduler state has been set to started, the scheduler would link itself to the task the start scheduler api has created. If the stop scheduler api was called immediately after the start scheduler api then this could lead the stop scheduler api cancelling the task without stopping the scheduler, as the scheduler could not have been linked to the task. Now the scheduler gets linked to the task before the scheduler state is set to started, fixing the problematic situation discribed above. Original commit: elastic/x-pack-elasticsearch@8334ae1967		2017-01-05 21:10:23 +01:00
buildSrc	Updates aws credential variables in upload task	2016-12-08 14:58:15 +00:00
elasticsearch	scheduler: prevent stopping scheduler before the scheduler was actually started	2017-01-05 21:10:23 +01:00
vagrant	Tweak Vagrant to use env variables for S3 boxes, update instructions	2016-10-11 11:07:41 -04:00
LICENSE.txt	Initial X-Pack commit	2018-04-20 14:16:58 -07:00
build.gradle	Moved the C++ code under the cpp sub-directory (elastic/elasticsearch#584)	2016-12-20 11:03:00 +00:00
gradle.properties	Upgrade to Elasticsearch 5.2 SNAPSHOT	2016-11-24 22:55:19 +00:00
settings.gradle	Creates a cpp gradle module to control the cpp build (elastic/elasticsearch#361)	2016-11-23 11:22:04 +00:00