Added version constants for 1.1.2 and 1.0.4
[TEST] make testTimeoutSendExceptionWithDelayedResponse more reliable on slow systems
[DOCS] Make snapshot repository examples consistent
[TEST] Use startNodesAsync in unicast discovery tests.
Update allocation.asciidoc
[BUILD] Fail release if test have AwaitsFix annotations

Note this commit upgrades Forbidden APIs to version 1.5

Closes #5807
Add a site plugin into list

Howdy,

Not sure if this is kosher but I would like to add my site plugin to the list in the docs.
[TEST] added sort by "_id" when score is the same to MultiMatchQueryTests#testEquivalence

A merge (and refresh) might rarely happen in the background between the two queries whose output is compared. It might then happen that two docs with same scores get returned by the two queries in a different order due to different lucene document id (which has changed in the meantime). To fix this we need to order by id when the score is the same, so that we can safely compare the output of the two queries (multimatch and dismax).
Moved the updateMappingOnMaster logic into a single place.

Closes #5798
[TEST] _id is not indexed by default, sort on score,_uid in MultiMatchQueryTests
Removed leading spaces on commented config key lines in elasticsearch.yml
Author: Sean Gallagher
Date: 17 Apr 2014 16:18 EDT

Removed spaces on commented lines containing config key entries to prevent
users from inadvertently messing up the indents in elasticsearch.yml.
Closes #5842
[TEST] Make InternalEngineMergeTests more stable
Fail replica shards locally upon failures

When a replication operation (index/delete/update) fails to be executed properly, we fail the replica and allow master to allocate a new copy of it. At the moment, the node hosting the primary shard is responsible of notifying the master of a failed replica. However, if the replica shard is initializing (`POST_RECOVERY` state), we have a racing condition between the failed shard message and moving the shard into the `STARTED` state. If the latter happen first, master will fail to resolve the fail shard message.

This commit builds on #5800 and fails the engine of the replica shard if a replication operation fails. This protects us against the above as the shard will reject the `STARTED` command from master. It also makes us more resilient to other racing conditions in this area.

Closes #5847
Upgrade to mvel 2.2.0.Final
closes #5877
Update forbidden-apis to 1.5.1 and remove the relaxed missing classes error.
A new ClusterStateStatus to indicate cluster state life cycles

When the ClusterService applies a new cluster state, it is first assigned as the new active one and then all listeners are called. Some of ES's features sample the current state and try to take action on it (for example index a document). If that fails, they will wait for change in the cluster state and try again (for example, wait for a shard to start and try indexing again).

If you're unlucky you sample the state after it has been assigned as the "active" state but before all listeners has done the work. In this cases the action take (i.e., indexing a doc) will still fail (as the shard is not yet started) but waiting for a new state may take a long time or fail.

 This commit adds a new ClusterStateStatus that allows to better track the stages a cluster state goes through (currently `RECEIVED`, `BEING_APPLIED` & `APPLIED`). This allows detecting that a cluster state is not yet fully applied and retry without waiting for a new state to arrive.

 This commits also adds a utility class , ClusterStateObserver, to make this pattern slightly simpler and avoid common pit falls.
Feedback round + some cleanup
Added ObservingContext to unify access to a couple of observing related variables.
minor tweak to make the code more readable
Bundeled lastObservedState and lastObservedStatus into a single class