Phase1 failed – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.2

Briefly, this error occurs when Elasticsearch is unable to complete the first phase of a snapshot operation, which involves creating a list of files to be included in the snapshot. This could be due to a variety of reasons such as insufficient disk space, network connectivity issues, or problems with the underlying file system. To resolve this issue, you can check the disk space and network connectivity, ensure the file system is functioning properly, and verify the snapshot repository’s configuration. If the problem persists, consider increasing the logging level to get more detailed information about the error.

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

Log Context

Log “phase1 failed” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 startingSeqNo = 0;
 try {
 final int estimateNumOps = shard.estimateNumberOfHistoryOperations("peer-recovery"; startingSeqNo);
 sendFileResult = phase1(phase1Snapshot.getIndexCommit(); shard.getGlobalCheckpoint(); () -> estimateNumOps);
 } catch (final Exception e) {
 throw new RecoveryEngineException(shard.shardId(); 1; "phase1 failed"; e);
 } finally {
 try {
 } catch (final IOException ex) {
 logger.warn("releasing snapshot caused exception"; ex);


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?