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

[Remote Store] Incorrect Recovery Type shown in _cat/recovery API when remote store is enabled. #10651

Open
Rishikesh1159 opened this issue Oct 16, 2023 · 3 comments
Assignees
Labels
bug Something isn't working good first issue Good for newcomers low hanging fruit Storage:Remote

Comments

@Rishikesh1159
Copy link
Member

Rishikesh1159 commented Oct 16, 2023

Describe the bug
With remote store enabled when a new replica is added to the cluster, the recovery type should be remote_store instead it gives peer as recovery type.

$ curl localhost:9200/_cat/recovery?v
index shard time type    stage source_host  source_node target_host  target_node repository snapshot files files_recovered files_percent files_total bytes bytes_recovered bytes_percent bytes_total translog_ops translog_ops_recovered translog_ops_percent
so  0   143ms empty_store done n/a      n/a     node-ip node-1   n/a    n/a   0   0        0.0%     0      0   0        0.0%     0      0      0           100.0%
so  0   4.7m peer    done node-ip node-1   node-ip node-3   n/a    n/a   1   1        100.0%    169     3776 3776      100.0%    36711602919 0      0           100.0%

To Reproduce
-> Create a index with some data.
-> Add new replica to the index
-> Call _cat/recovery and check the output.

Expected behavior
The recovery type must be remote_store not peer

Plugins
Please list all plugins currently enabled.

Screenshots
If applicable, add screenshots to help explain your problem.

Host/Environment (please complete the following information):

  • OS: [e.g. iOS]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@Bukhtawar
Copy link
Collaborator

We decided on further fine tuning statuses to add replica recovery to be more specific so as to not tie recovery to the source but rather talk about what kind of recovery it stands for.

@sachinpkale
Copy link
Member

[Storage Triage - attendees 1 2 3 4 5 6 7 8 9 10 ]

Based on the priority, we are putting it in Ready to be picked

@sachinpkale sachinpkale moved this from 🆕 New to Ready To Be Picked in Storage Project Board May 30, 2024
@srikanthpadakanti
Copy link
Contributor

srikanthpadakanti commented Jun 26, 2024

@sachinpkale @Bukhtawar
Please assign this to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers low hanging fruit Storage:Remote
Projects
Status: Ready To Be Picked
Development

No branches or pull requests

4 participants