Briefly, this error occurs when Elasticsearch receives a request to delete a snapshot, but the request is not acknowledged. This could be due to a network issue, a timeout, or the snapshot may not exist. To resolve this issue, you can try the following: 1) Check the network connection between the client and the Elasticsearch server. 2) Increase the timeout value for the delete snapshot request. 3) Verify that the snapshot you are trying to delete actually exists in the repository.
This guide will help you check for common problems that cause the log ” [{}] snapshot [{}] delete issued but the request was not acknowledged ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: snapshot, request, plugin, delete.
Log Context
Log “[{}] snapshot [{}] delete issued but the request was not acknowledged” classname is SnapshotRetentionTask.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
client.admin().cluster().prepareDeleteSnapshot(repo; snapshot.getName())
.execute(new LatchedActionListener(ActionListener.wrap(acknowledgedResponse -> {
if (acknowledgedResponse.isAcknowledged()) {
logger.debug("[{}] snapshot [{}] deleted successfully"; repo; snapshot);
} else {
logger.warn("[{}] snapshot [{}] delete issued but the request was not acknowledged"; repo; snapshot);
}
slmStats.snapshotDeleted(slmPolicy);
listener.onResponse(acknowledgedResponse);
};
e -> {
