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 OpenSearch starts the process of cloning a snapshot. It’s not an error message, but an informational log indicating that a snapshot clone operation has begun. If this operation is not intended or causing issues, you can resolve it by stopping the snapshot clone operation. Alternatively, you can check your OpenSearch configuration to ensure that automatic snapshot cloning is not enabled if it’s not required. Also, ensure that your storage space is sufficient to handle the snapshot clone operation to prevent any potential 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 ” snapshot clone [{}] started ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: snapshot.
Log Context
Log “snapshot clone [{}] started” classname is SnapshotsService.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
listener.onFailure(e);
}
@Override
public void clusterStateProcessed(String source; ClusterState oldState; final ClusterState newState) {
logger.info("snapshot clone [{}] started"; snapshot);
addListener(snapshot; ActionListener.wrap(r -> listener.onResponse(null); listener::onFailure));
startCloning(repository; newEntry);
}
@Override
