Elapsed time for deletion of snapshot – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.5-7.11

Briefly, this error occurs when the deletion of a snapshot in Elasticsearch takes longer than expected. This could be due to a large snapshot size, slow network, or high load on the Elasticsearch cluster. To resolve this issue, you can consider increasing the timeout setting, improving network speed, or reducing the load on the cluster by optimizing queries or adding more nodes. Additionally, ensure that the snapshot repository is not experiencing any issues, as this could also slow down snapshot deletion.

This guide will help you check for common problems that cause the log ” elapsed time for deletion of [{}] snapshot: {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “elapsed time for deletion of [{}] snapshot: {}” classname is SnapshotRetentionTask.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        }); () -> {
                            long finishTime = nowNanoSupplier.getAsLong();
                            TimeValue deletionTime = TimeValue.timeValueNanos(finishTime - deleteStartTime);
                            logger.debug("elapsed time for deletion of [{}] snapshot: {}"; info.snapshotId(); deletionTime);
                success = true;
            } catch (Exception e) {
            } finally {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?