Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce a new use_synthetic_source_recovery track parameter #713

Conversation

salvatore-campagna
Copy link
Contributor

PR elastic/elasticsearch#114618 in Elasticsearch introduced the ability
to do recovery using synthetic source instead of using the _recovery_source field.

We are updating three Rally tracks, elastic/logs, elastic/security and tsdb to include a new parameter, use_synthetic_source_recovery. This parameter will allow us to toggle the index.mapping.use_synthetic_source
setting in Rally nightly benchmarks. We will follow-up with another PR introducing new nightly Elasticsearch benchmarks
to provide a means of comparing the performance impact of enabling versus disabling this setting.

Copy link
Member

@martijnvg martijnvg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - one nit about parameter description.

@@ -222,6 +222,7 @@ The following parameters are available:
* `workflow-request-cache` (default: `true`) - Explicit control of request cache query parameter in searches executed in a workflow. This can be further overriden at an operation level with `request-cache` parameter.
* `synthetic_source_keep` (default: unset) - Allows overriding the default synthetic source behaviour for all field types with the following values: `none` (equivalent to unset) - no source is stored, `arrays` - source stored as is only for multi-value (array) fields.
* `source_mode` (default: unset) - Specifies the source mode to be used.
* `use_synthetic_source_recovery` (default: unset): If `true` recovery will take place using synthetic source instead of using `_recovery_source`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* `use_synthetic_source_recovery` (default: unset): If `true` recovery will take place using synthetic source instead of using `_recovery_source`
* `use_synthetic_source_recovery` (default: unset): Whether synthetic recovery source will be used.

@salvatore-campagna salvatore-campagna merged commit cbce57a into elastic:master Dec 18, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants