Failed to purge – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to purge ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “failed to purge” classname is IndicesTTLService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     bulkRequest.add(new DeleteRequest().index(shardToPurge.routingEntry().index()).type(docToPurge.type).id(docToPurge.id).version(docToPurge.version).routing(docToPurge.routing));
                    bulkRequest = processBulkIfNeeded(bulkRequest; false);
                }
                processBulkIfNeeded(bulkRequest; true);
            } catch (Exception e) {
                logger.warn("failed to purge"; e);
            } finally {
                searcher.close();
            }
        }
    }




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content