Master failover before deleted snapshot could complete – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.8-7.17

Briefly, this error occurs when a snapshot deletion process in Elasticsearch is interrupted due to a master node failover. This could be due to network issues, hardware failure, or the master node being overwhelmed. To resolve this, you can manually delete the snapshot again after the new master node is elected. Also, ensure your cluster’s health is stable to prevent frequent master failovers. Additionally, consider increasing the master node’s resources to handle the load and avoid failures.

This guide will help you check for common problems that cause the log ” master failover before deleted snapshot could complete ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: master, failover, snapshot.

Log Context

Log “master failover before deleted snapshot could complete” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        createDeleteStateUpdate(outstandingDeletes; repositoryName; result.v1(); Priority.IMMEDIATE; listener)
                }; e -> {
                    if (ExceptionsHelper.unwrap(e; NotMasterException.class; FailedToCommitClusterStateException.class) != null) {
                        logger.warn("master failover before deleted snapshot could complete"; e);
                        // Just pass the exception to the transport handler as is so it is retried on the new master
                    } else {
                        logger.warn("deleted snapshot failed"; e);


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?