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.

Sign up for GitHub

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

Jump to bottom

Persist all engine failure exceptions #12168

Closed
wants to merge 1 commit into from
Closed

Persist all engine failure exceptions #12168

wants to merge 1 commit into from
+133 −21

Commits on Jul 9, 2015

  1. Persist all engine failure exceptions 

    Currently when an engine fails the shard state file is no longer deleted elastic#11933
and the underlying store is only marked as corrupted for index corruption exceptions.
This means that the store can be opened, even after it failed with IOE, OOM exceptions.

It would be useful to persist the engine failures that are not due to corruption for
inspection, these can be exposed later through elastic#11545
    @areek
    areek committed Jul 9, 2015
    Configuration menu
    Copy the full SHA
    6c6d05c View commit details
    Browse the repository at this point in the history