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

Reindex share retry between hit sources (#44203) #45348

Merged

Conversation

henningandersen
Copy link
Contributor

The client and remote hit sources had each their own retry mechanism,
which would do the same. Supporting resiliency we would have to expand
on the retry mechanisms and as a preparation for that, the retry
mechanism is now shared such that each sub class is only responsible for
sending requests and converting responses/failures to common format.

Part of #42612

Backport of #44203, need the test runs due to conflicts.

The client and remote hit sources had each their own retry mechanism,
which would do the same. Supporting resiliency we would have to expand
on the retry mechanisms and as a preparation for that, the retry
mechanism is now shared such that each sub class is only responsible for
sending requests and converting responses/failures to common format.

Part of elastic#42612
@henningandersen henningandersen added >non-issue backport :Distributed/Reindex Issues relating to reindex that are not caused by issues further down v7.4.0 labels Aug 8, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@henningandersen henningandersen merged commit d139896 into elastic:7.x Aug 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport :Distributed/Reindex Issues relating to reindex that are not caused by issues further down >non-issue v7.4.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants