We manage to occasionally put ES cluster into a particular state, where it
would fail to restore index from a valid snapshot with 404 and:
This is an exact quote, note '_snapshot', which is not the name of the
index. Nothing in the main logs.
The very same restore operation (i.e. same command) would work one hour and
fail the next.
As far as we observed, it usually follows series of snapshot / restore
operations, when some of the indices would be closed to allow restore to
happen and then be reopened. It is possible that we call 'open' and 'close'
on indices that are already in the intended state, although not sure if
this is relevant.
Not sure if related, but at the same time trying to list all snapshots in a
repository ( by say getting
ends up with Nginx 502-ing. Again, nothing in the logs.
At the moment, we're still trying to figure out the possible cause, but
would be grateful for any advice if anyone might have experienced this
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/60d2f784-a51b-4e42-b40f-409bbf895b9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.