Briefly, this error occurs when a snapshot clone operation is initiated in Elasticsearch. It’s not an error message, but an informational message indicating that the process of cloning a snapshot has begun. This is part of the backup and restore functionality of Elasticsearch. If this operation was not intended, it can be stopped by deleting the clone using the delete snapshot API. However, if it was intended but is causing issues, you may need to check your cluster health, ensure you have sufficient storage space, or verify the snapshot repository configuration.
This guide will help you check for common problems that cause the log ” snapshot clone [{}] started ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: snapshot.
Log Context
Log “snapshot clone [{}] started” classname is SnapshotsService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
listener.onFailure(e);
}
@Override
public void clusterStateProcessed(ClusterState oldState; final ClusterState newState) {
logger.info("snapshot clone [{}] started"; snapshot);
addListener(snapshot; listener.delegateFailureAndWrap((l; r) -> l.onResponse(null)));
startCloning(repository; newEntry);
}
}; "clone_snapshot [" + request.source() + "][" + snapshotName + ']'; listener::onFailure);
}
