-
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
Prioritize recovery of system indices #61660
Comments
Pinging @elastic/es-distributed (:Distributed/Recovery) |
@jaymode Does this issue only seek to change the current recovery order? Do we also need to think about preventing non-system indices from beginning recovery until the system indices have completed? It looks like |
@pugnascotia I think we should allow for concurrent system and non-system index recoveries. |
Closes elastic#61660. When ordering shard for recovery, ensure system index shards are ordered first.
Closes #61660. When ordering shard for recovery, ensure system index shards are ordered first so that their recovery will be started first. Note that I rewrote PriorityComparatorTests to use IndexMetadata instead of its local IndexMeta POJO.
Closes #61660. When ordering shard for recovery, ensure system index shards are ordered first so that their recovery will be started first. Note that I rewrote PriorityComparatorTests to use IndexMetadata instead of its local IndexMeta POJO.
During startup, system indices should be prioritized over the recovery of normal indices/user data so that the stack may be fully operational once user data is recovered.
Going beyond that, system indices themselves may need to be prioritized in terms of recovery operations as some system components may depend on others. We may be able to reuse the
order
that exists on indices today in terms of prioritizing which system indices get recovered first.The text was updated successfully, but these errors were encountered: