Releasing snapshot caused exception – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch encounters an issue while trying to release a snapshot. This could be due to a variety of reasons such as insufficient permissions, network connectivity issues, or problems with the underlying storage system. To resolve this issue, you can check the Elasticsearch logs for more detailed error messages. Ensure that Elasticsearch has the necessary permissions to access the snapshot repository. Also, verify the network connectivity and the health of the storage system where the snapshots are stored.

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

Log Context

Log “releasing snapshot caused exception” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                sendFileStep.addListener(ActionListener.wrap(r -> IOUtils.close(safeCommitRef; releaseStore); e -> {
                    try {
                        IOUtils.close(safeCommitRef; releaseStore);
                    } catch (Exception ex) {
                        logger.warn("releasing snapshot caused exception"; ex);

                // If the target previously had a copy of this shard then a file-based recovery might move its global checkpoint
                // backwards. We must therefore remove any existing retention lease so that we can create a new one later on in the