-
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
Removing remote cluster that is in use by auto-follow pattern causes crash #36667
Labels
Comments
cjcenizal
added
blocker
:Distributed/CCR
Issues around the Cross Cluster State Replication features
labels
Dec 15, 2018
Pinging @elastic/es-distributed |
CC @jasontedor |
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Dec 16, 2018
Both index following and auto following should be resilient against missing remote connections. This happens in the case that they get accidentally removed by a user. When this happens auto following and index following will retry to continue instead of failing with unrecoverable exceptions. Both the put follow and put auto follow APIs validate whether the remote cluster connection. The logic added in this change only exists in case during the lifetime of a follower index or auto follow pattern the remote connection gets removed. This retry behaviour similar how CCR deals with authorization errors. Closes elastic#36667 Closes elastic#36255
martijnvg
added a commit
that referenced
this issue
Dec 24, 2018
Both index following and auto following should be resilient against missing remote connections. This happens in the case that they get accidentally removed by a user. When this happens auto following and index following will retry to continue instead of failing with unrecoverable exceptions. Both the put follow and put auto follow APIs validate whether the remote cluster connection. The logic added in this change only exists in case during the lifetime of a follower index or auto follow pattern the remote connection gets removed. This retry behavior similar how CCR deals with authorization errors. Closes #36667 Closes #36255
martijnvg
added a commit
that referenced
this issue
Dec 24, 2018
Both index following and auto following should be resilient against missing remote connections. This happens in the case that they get accidentally removed by a user. When this happens auto following and index following will retry to continue instead of failing with unrecoverable exceptions. Both the put follow and put auto follow APIs validate whether the remote cluster connection. The logic added in this change only exists in case during the lifetime of a follower index or auto follow pattern the remote connection gets removed. This retry behavior similar how CCR deals with authorization errors. Closes #36667 Closes #36255
martijnvg
added a commit
that referenced
this issue
Dec 24, 2018
Both index following and auto following should be resilient against missing remote connections. This happens in the case that they get accidentally removed by a user. When this happens auto following and index following will retry to continue instead of failing with unrecoverable exceptions. Both the put follow and put auto follow APIs validate whether the remote cluster connection. The logic added in this change only exists in case during the lifetime of a follower index or auto follow pattern the remote connection gets removed. This retry behavior similar how CCR deals with authorization errors. Closes #36667 Closes #36255
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I have a remote cluster which is in use by a CCR auto-follow pattern:
GET _remote/info
:GET _ccr/auto_follow
:When I remove the remote cluster, ES throws repeated errors until it crashes with
ERROR ES exited with code 126
:The text was updated successfully, but these errors were encountered: