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
Unfollowing a follower index that has had its remote cluster deleted throws 500 error #71885
Labels
>bug
:Distributed/CCR
Issues around the Cross Cluster State Replication features
Team:Distributed
Meta label for distributed team
Comments
cjcenizal
added
>bug
:Distributed/CCR
Issues around the Cross Cluster State Replication features
labels
Apr 19, 2021
Pinging @elastic/es-distributed (Team:Distributed) |
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
Apr 20, 2021
We remove the retention leases from the leader cluster after processing the cluster state update in the unfollow action, but today we assume that we're still connected to the leader cluster when doing so. If the leader cluster has been removed then `Client#getRemoteClusterClient` throws an exception, which means the listener is never notified of the failure. This commit addresses this by catching the exception, logging a warning, and routing the exception back to the client. Closes elastic#71885
DaveCTurner
added a commit
that referenced
this issue
Apr 20, 2021
We remove the retention leases from the leader cluster after processing the cluster state update in the unfollow action, but today we assume that we're still connected to the leader cluster when doing so. If the leader cluster has been removed then `Client#getRemoteClusterClient` throws an exception, which means the listener is never notified of the failure. This commit addresses this by catching the exception, logging a warning, and routing the exception back to the client. Closes #71885
DaveCTurner
added a commit
that referenced
this issue
Apr 20, 2021
We remove the retention leases from the leader cluster after processing the cluster state update in the unfollow action, but today we assume that we're still connected to the leader cluster when doing so. If the leader cluster has been removed then `Client#getRemoteClusterClient` throws an exception, which means the listener is never notified of the failure. This commit addresses this by catching the exception, logging a warning, and routing the exception back to the client. Closes #71885
DaveCTurner
added a commit
that referenced
this issue
Apr 20, 2021
We remove the retention leases from the leader cluster after processing the cluster state update in the unfollow action, but today we assume that we're still connected to the leader cluster when doing so. If the leader cluster has been removed then `Client#getRemoteClusterClient` throws an exception, which means the listener is never notified of the failure. This commit addresses this by catching the exception, logging a warning, and routing the exception back to the client. Closes #71885
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Distributed/CCR
Issues around the Cross Cluster State Replication features
Team:Distributed
Meta label for distributed team
Discovered via elastic/kibana#68711. To reproduce, create a follower index, remove its remote cluster, and then try to unfollow the follower index.
The ES logs will show this type of error and stacktrace:
The text was updated successfully, but these errors were encountered: