-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[CCR] Follower info API doesn't return paused status #37738
Labels
Comments
jen-huang
added
the
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
label
Jan 23, 2019
Pinging @elastic/es-distributed |
This does not seem to be an issue if both indices are paused:
|
Hmm, if I request for just the paused index (
|
@jen-huang That is related to the bug in the issue description. Index filtering is just completely broken. I will have a PR open soon. |
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Jan 23, 2019
The filtering by follower index was completely broken. Also the wrong persistent tasks were selected, causing the wrong status to be reported. Closes elastic#37738
martijnvg
added a commit
that referenced
this issue
Jan 24, 2019
The filtering by follower index was completely broken. Also the wrong persistent tasks were selected, causing the wrong status to be reported. Closes #37738
martijnvg
added a commit
that referenced
this issue
Jan 24, 2019
The filtering by follower index was completely broken. Also the wrong persistent tasks were selected, causing the wrong status to be reported. Closes #37738
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I have two active follower indices:
copy-of-kibana_sample_data_logs
,copy-of-kibana_sample_data_flights
.Then I send a request to pause the second one:
Follower stats API does not show the index that was paused (correct behavior):
However, the follower info API still returns
status: "active"
for it:cc @martijnvg
The text was updated successfully, but these errors were encountered: