-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
Labels
:Distributed/CCR
Issues around the Cross Cluster State Replication features
Comments
martijnvg
added
the
:Distributed/CCR
Issues around the Cross Cluster State Replication features
label
Jul 5, 2018
Pinging @elastic/es-distributed |
29 tasks
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Jul 10, 2018
martijnvg
added a commit
that referenced
this issue
Jul 17, 2018
martijnvg
added a commit
that referenced
this issue
Jul 17, 2018
Closed by #31930 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: