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

Prioritizing shard recoveries #10069

Closed
avleen opened this issue Mar 12, 2015 · 3 comments
Closed

Prioritizing shard recoveries #10069

avleen opened this issue Mar 12, 2015 · 3 comments

Comments

@avleen
Copy link

avleen commented Mar 12, 2015

Feature request:

When multiple shard replicas need recovery (eg, when you restart the whole cluster), it can be beneficial to get some indices green before others.
In the Logstash case, getting the most recent indices by date.
In other cases, there may be application demands on which index you really need back first.

Being able to set a specific priority on indices, or have it automatically determined for date-based indices, would be quite helpful.

@s1monw
Copy link
Contributor

s1monw commented Mar 12, 2015

once we fixed #10032 this will be much easier since we can recover unsealed shards first or even last since all the sealed once are instant and you problem will be going away entirely.

@kadaan
Copy link

kadaan commented Mar 17, 2015

#10032 may not address the full request as certain indices may be more important for a business then others. Ideally, ES could take this priority into consideration when determining which shards to recover given limited recovery resources.

@clintongormley
Copy link
Contributor

Closing in favour of #11787

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants