Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.
Briefly, this error occurs when a master node failover happens in OpenSearch while a snapshot deletion process is ongoing. This can lead to inconsistencies in the snapshot repository. To resolve this issue, you can manually delete the snapshot from the repository. Alternatively, you can try to restart the master node, or increase the master node’s stability to prevent frequent failovers. Lastly, ensure that your cluster state is healthy before initiating snapshot deletion to avoid such issues.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
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 OpenSearch concepts: master, snapshot, failover.
Log Context
Log “master failover before deleted snapshot could complete” classname is SnapshotsService.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
"delete snapshot";
createDeleteStateUpdate(outstandingDeletes; repoName; 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
listener.onFailure(e);
} else {
logger.warn("deleted snapshot failed"; e);
listener.onFailure(
