TTL deletion failures are not logged #11019
Assignees
Labels
Comments
clintongormley
added
discuss
>enhancement
help wanted
spinscale
added a commit
to spinscale/elasticsearch
that referenced
this issue
May 22, 2015
In order to get some information if the TTL purger thread could successfully delete all documents per bulk exection, this commit adds some logging. TRACE level logging will potentially contain a lot of information about all the bulk failures. Closes elastic#11019
spinscale
added a commit
to spinscale/elasticsearch
that referenced
this issue
May 22, 2015
In order to get some information if the TTL purger thread could successfully delete all documents per bulk exection, this commit adds some logging. TRACE level logging will potentially contain a lot of information about all the bulk failures. Closes elastic#11019
spinscale
added a commit
to spinscale/elasticsearch
that referenced
this issue
May 22, 2015
In order to get some information if the TTL purger thread could successfully delete all documents per bulk exection, this commit adds some logging. TRACE level logging will potentially contain a lot of information about all the bulk failures. Closes elastic#11019
spinscale
added a commit
that referenced
this issue
May 22, 2015
In order to get some information if the TTL purger thread could successfully delete all documents per bulk exection, this commit adds some logging. TRACE level logging will potentially contain a lot of information about all the bulk failures. Closes #11019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
IndicesTTLServiceuses a bulk request to perform the deletions of expired documents. Sometimes these deletions could fail, but the service does not log or provide any indication that the deletions are failing.The
onResponsemethod could check to see if the response had any failures and if so log the failures with the details. Additionally, theonFailuremethod looks like it will just swallow the Throwable that caused the failure.The text was updated successfully, but these errors were encountered: