-
Notifications
You must be signed in to change notification settings - Fork 306
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
Skip document_already_exists_exception logging #423
Comments
Closed by #424 |
This feature doesnt seem to work in logstash 5.2.2 - also it is not clear if its the statuscode you "whitelist" to blacklist it from the logoutput or if its the error type string. [2017-03-28T07:45:10,263][INFO ][logstash.outputs.elasticsearch] retrying failed action with response code: 429 ({"type"=>"es_rejected_execution_exception", "reason"=>"rejected execution of org.elasticsearch.transport.TransportService$4@5ccf9d0f on EsThreadPoolExecutor[bulk, queue capacity = 50, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@4c64817c[Running, pool size = 18, active threads = 18, queued tasks = 562, completed tasks = 47167573]]"}) |
@SuperFunks may be broken in 5.2.2 , but you should be able to add the specific error, in this case The documentation is here: https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html#plugins-outputs-elasticsearch-failure_type_logging_whitelist . And the test with the example is here: https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/424/files#diff-fcc0c3ab23ddc8b47ed814f1a7b88ea4R45. |
When a document already exists, and we do not want to update the content, we should use the
create
method in the elasticsearch output. This fils up the disk when a lot of documents already exists. In case someone doesn't care about this being logged, we should check the status, and the type of the exception to avoid logging this type of exceptions:I propose a new configuration called
skip_error
which takes a string that is the error type (in this casedocument_already_exists_exception
) so we don't log it.The text was updated successfully, but these errors were encountered: