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

Don't set retries for restore snapshot #799

Conversation

danielmitterdorfer
Copy link
Member

With this commit we use the standard retry handling from the
Elasticsearch client. Previously, we've implemented a special logic to
add a retries parameter but it is ineffective and instead is passed a
request parameter to Elasticsearch.

With this commit we use the standard retry handling from the
Elasticsearch client. Previously, we've implemented a special logic to
add a `retries` parameter but it is ineffective and instead is passed a
request parameter to Elasticsearch.
@danielmitterdorfer danielmitterdorfer added bug Something's wrong :Load Driver Changes that affect the core of the load driver such as scheduling, the measurement approach etc. labels Oct 17, 2019
@danielmitterdorfer danielmitterdorfer added this to the 1.4.0 milestone Oct 17, 2019
@danielmitterdorfer danielmitterdorfer self-assigned this Oct 17, 2019
Copy link
Contributor

@dliappis dliappis left a comment

Choose a reason for hiding this comment

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

Given the lack of alternatives, LGTM

@danielmitterdorfer danielmitterdorfer merged commit 864f0c5 into elastic:master Oct 18, 2019
@danielmitterdorfer danielmitterdorfer deleted the no-retry-for-restore-snapshot branch October 18, 2019 09:24
dliappis added a commit that referenced this pull request Oct 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something's wrong :Load Driver Changes that affect the core of the load driver such as scheduling, the measurement approach etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants