[TEST] cat.recovery with replicas can have 100.0%
[DOCS] fixed typo in multi term vectors docs
[DOCS] fixed broken json in multi term vectors docs
[TEST] Enforce that only one shard per node is allocated. The prevents during node shutdown, that a second shard is assigned the another node.
mute this test until we fix isFinite
[TEST] Temporarily added a wait-for-yellow to delete_mapping tests

Should be removed once #5997 is fixed
Provided some insights as to how More Like This works internally.

In the Google Groups forum there appears to be some confusion as to what mlt
does. This documentation update should hopefully help demystifying this
feature, and provide some understanding as to how to use its parameters.

Closes #6092
Added the ability to include the queried document for More Like This API.

By default More Like This API excludes the queried document from the response.
However, when debugging or when comparing scores across different queries, it
could be useful to have the best possible matched hit. So this option lets users
explicitly specify the desired behavior.

Closes #6067
Add /_cat/fielddata to display fielddata usage

Closes #4593
Fix typo in path specification for /_cat/fielddata
[TEST] Removed the restriction on the number of bool clauses that must match.

The test failed because 'percent_terms_to_match' defaults to 0.3, which results
in requiring that some terms only found in the queried document must match, when
all the documents are on the same shard.
[TEST] randomly added node.bench=true to client node in test cluster and re-enabled REST benchmark tests based on number of bench nodes available

In our REST tests we already have support for features and skip sections that allow to skip tests if a feature is not supported.
We can then add a skip section based on the benchmark feature to the benchmark tests and execute them only when they are supported, knowing that they need at least a node with node.bench settings within the cluster. We can check that this requirement is met by calling the nodes info api.

This way we can dynamically decide whether to execute those tests or not and we don't need to have a node.bench around all the time. In fact, given that the REST tests use the GLOBAL cluster, we want to be able to randomize settings as much as possible and run tests against default settings as well. Also, this mechanism can be easily supported by the external cluster implementation that is used during the release process.

Introduced ability to disable benchmark nodes which is needed by BenchmarkNegativeTest.
[TEST] Add test specifying fields field /_cat/fielddata REST test
don't call isFinite from XAnalyzingSuggester; re-enable test on Java 8
[TEST] Fix for benchmark tests

- Fix bug where repeatedly calling computeSummaryStatistics() could
  accumulate some values incorrectly
- Fix check for number of responsive nodes on list is <= number of
  candidate benchmark nodes
- Add public getters for summary statistics
- Add javadoc for new getters
- Add javadoc comments about API use
- Improve abort and status tests by calling awaitBusy() to wait for jobs
  to be completely submitted before testing them
Fixed typos in FieldSortBuilder
enable dynamic scripts in release node, otherwise REST tests will fail

Relates to #5853
[TEST] Aborting a non-existent benchmark throws a missing request
add failing test for shard_min_doc_count
refactor: unify terms and significant_terms parsing