Recovery API #5239
Closed
Recovery API #5239
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| builder.field("primary", primary); | ||
| builder.field("start_time", timer.startTime == 0 ? 0 : dateFormatter.print(timer.startTime)); | ||
| builder.field("stop_time", timer.stopTime == 0 ? 0 : dateFormatter.print(timer.stopTime)); | ||
| builder.field("total_time_in_millis", timer.time); |
There was a problem hiding this comment.
For bytes and time values we typically use byteSizeField and timeValueField methods that support human flag. You can also optimize the code by using XContentBuilderString instead of string constants. MergeStats is a good example.
Adds a new API endpoint at /_recovery as well as to the Java API. The recovery API allows one to see the recovery status of all shards in the cluster. It will report on percent complete, recovery type, and which files are copied. Closes #4637
`_exists_` and `_missing_` miss field name expansion that `exists` and `missing` have, which allows these filters to work on `object` fields. Close #5142
Adds support for storing mustache based query templates that can later be filled with query parameter values at execution time. Templates may be both quoted, non-quoted and referencing templates stored in config/scripts/*.mustache by file name. See docs/reference/query-dsl/queries/template-query.asciidoc for templating examples. Implementation detail: mustache itself is being shaded as it depends directly on guava - so having it marked optional but included in the final distribution raises chances of version conflicts downstream. Fixes #4879
When running tests for site plugins, it could happen that the REST Service is not fully started and not ready immediately to serve HTTP requests. It gives `503 Service Unavailable` error in that case. This patch will gives 5 seconds before failing the test.
…ame + required Value Source type as a combi key (used to be only field name). This fixes a problem where multiple aggregations where defined on the same field, yet require different types of value sources. Closes #5190
Fixes #5128 Remove java 7 specific Locale functions, add "coming[1.1.0]" to documentation add LocaleUtils utility class for dealing with Locale functions
…date_/histogram aggregation was defined on unmapped field and also had a sub aggregation. The root cause there was that in such case, the estimated bucket count was 0, and the code was not designed to handle that well. Closes #5179
(cherry picked from commit f26a369)
Pages are now going to be reused when the size of the array is greater than
${page_size}/2 (as opposed to ${page_size} currently).
Close #5299
…lists in our REST tests
A new metric aggregation that can compute approximate values of arbitrary percentiles. Close #5323
Today, even though our merge policy doesn't return new merge specs on SEGMENT_FLUSH, merge on the scheduler is still called on flush time, and can cause merges to stall indexing during merges. Both for the concurrent merge scheduler (the default) and the serial merge scheduler. This behavior become worse when throttling kicks in (today at 20mb per sec). In order to solve it (outside of Lucene for now), we wrap the merge scheduler with an EnableMergeScheduler, where, on the thread level, using a thread local, the call to merge can be enabled/disabled. A Merges helper class is added where all explicit merges operations should go through. If the scheduler is the enabled one, it will enable merges before calling the relevant explicit method call. In order to make sure Merges is the only class that calls the explicit merge calls, the IW variant of them is added to the forbidden APIs list. closes #5319
Closes #5346
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a new API endpoint at /_recovery as well as to the Java API. The
recovery API allows one to see the recovery status of all shards in the
cluster. It will report on percent complete, recovery type, and which
files are copied.
Closes #4637