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

Handle no-op document level failures #46083

Merged
merged 2 commits into from
Aug 28, 2019
Merged

Handle no-op document level failures #46083

merged 2 commits into from
Aug 28, 2019

Commits on Aug 28, 2019

  1. Handle no-op document level failures 

    Today we assume that document failures can not occur for no-ops. This
assumption is bogus, as they can fail for a variety of reasons such as
the Lucene index having reached the document limit. Because of this
assumption, we were asserting that such a document-level failure would
never happen. When this bogus assertion is violated, we fail the node, a
catastrophe. Instead, we need to treat this as a fatal engine exception.
    @jasontedor
    jasontedor committed Aug 28, 2019
    Configuration menu
    Copy the full SHA
    2eccc6a View commit details
    Browse the repository at this point in the history

  2. Merge branch 'master' into no-op-document-level-failure

    @elasticmachine
    elasticmachine authored Aug 28, 2019
    Configuration menu
    Copy the full SHA
    9314980 View commit details
    Browse the repository at this point in the history