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.

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

Reduce log level for pipeline failure #54097

Commits on Mar 24, 2020

  1. Reduce log level for pipeline failure

    Today we log `failed to execute pipeline for a bulk request` at `ERROR` level
    if an attempt to run an ingest pipeline fails. A failure here is commonly due
    to an `EsRejectedExecutionException`. We also feed such failures back to the
    client and record the rejection in the threadpool statistics.
    
    In line with elastic#51459 there is no need to log failures within actions so noisily
    and with such urgency. It is better to leave it up to the client to react
    accordingly. Typically an `EsRejectedExecutionException` should result in the
    client backing off and retrying, so a failure here is not normally fatal enough
    to justify an `ERROR` log at all.
    
    This commit reduces the log level for this message to `DEBUG`.
    DaveCTurner committed Mar 24, 2020
    Configuration menu
    Copy the full SHA
    fbb2a2f View commit details
    Browse the repository at this point in the history