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

Improve shard follow task retry mechanism #31816

Closed
martijnvg opened this issue Jul 5, 2018 · 2 comments
Closed

Improve shard follow task retry mechanism #31816

martijnvg opened this issue Jul 5, 2018 · 2 comments
Labels
:Distributed/CCR Issues around the Cross Cluster State Replication features

Comments

@martijnvg
Copy link
Member

Currently there is one simple counter for counting retries caused by remote failures when invoking shard changes, updating mapping (cluster state api and put mapping api), bulk shard operations api.

The shard follow task api likely needs multiple counters per read / write, so that an unstable network does not cause to immediately fail the shard follow task.

Things to do and investigate:

Relates to #30086

@martijnvg martijnvg added the :Distributed/CCR Issues around the Cross Cluster State Replication features label Jul 5, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@jasontedor
Copy link
Member

Closed by #31930

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/CCR Issues around the Cross Cluster State Replication features
Projects
None yet
Development

No branches or pull requests

3 participants