Mount snapshot response failed to complete got response – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.8-8.9

Briefly, this error occurs when Elasticsearch fails to complete the process of mounting a snapshot, possibly due to network issues, insufficient permissions, or a corrupted snapshot. To resolve this, you can try the following: 1) Check your network connection and ensure the Elasticsearch cluster is accessible. 2) Verify that Elasticsearch has the necessary permissions to access the snapshot repository. 3) Check the integrity of the snapshot and consider creating a new one if it’s corrupted. 4) Ensure that the Elasticsearch cluster has sufficient resources to complete the operation.

This guide will help you check for common problems that cause the log ” mount snapshot response failed to complete; got response ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: response, plugin, snapshot.

Log Context

Log “mount snapshot response failed to complete; got response” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 listener.delegateFailureAndWrap((l; response) -> {
 if (response.status() != RestStatus.OK && response.status() != RestStatus.ACCEPTED) {
 logger.debug("mount snapshot response failed to complete");
 throw new ElasticsearchException("mount snapshot response failed to complete; got response " + response.status());