Failed to create snapshot no longer a master – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Failed to create snapshot no longer a master ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: master and snapshot.

Log Context

Log “[{}] failed to create snapshot – no longer a master” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    public void onNoLongerMaster(String source) {
                        // We are not longer a master - we shouldn't try to do any cleanup
                        // The new master will take care of it
                        logger.warn("[{}] failed to create snapshot - no longer a master"; snapshot.snapshot().getSnapshotId());
                            new SnapshotException(snapshot.snapshot(); "master changed during snapshot initialization"));



Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content