-
Notifications
You must be signed in to change notification settings - Fork 122
Automatically clean up after failed indexing runs #402
Comments
Can I work on this issue? |
Can i work on this issue? |
@hedonhermdev go ahead. @CodeMonk263 please find another issue to work on since @hedonhermdev commented first. |
@hedonhermdev are still working on this issue? |
No.
…On Sat, 29 Feb 2020 at 8:07 PM, Dantraz ***@***.***> wrote:
@hedonhermdev <https://github.com/hedonhermdev> are still working on this
issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#402>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFRPNJ5THFLEUXK4JO5K42TRFEORJANCNFSM4KGJ2ZYQ>
.
|
Can i take it over? |
Go ahead @DantrazTrev |
@DantrazTrev are u still working on this? |
@tushar912 it's been a few months since @DantrazTrev's post, I think you can go ahead and work on this. |
Ok |
The way i understood this issue is as follows. The main indexing job is done by |
Also i am thinking of modifying the already existing |
When an indexing job fails (such as if a node in our Elasticsearch cluster has a full disk, or a bug in indexer-worker halts the process), the incomplete index is left inside of the Elasticsearch cluster, requiring someone to manually delete it. The indexer should detect this condition when the job starts and handle it.
The production index is determined by the
image
alias. The indexer should delete any index NOT pointed to by this alias following the naming schemeimage-<uuid>
.The text was updated successfully, but these errors were encountered: