Briefly, this error occurs when Elasticsearch attempts to resume an interrupted blob upload but encounters issues. This could be due to network instability, insufficient storage space, or problems with the blob storage service. To resolve this, you can try increasing your storage space, improving your network connection, or checking the health of your blob storage service. If the problem persists, consider breaking the blob into smaller parts for easier upload or reinitiating the upload session.
This guide will help you check for common problems that cause the log ” Retrying broken resumable upload session for blob {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repository-gcs, repositories.
Overview
An Elasticsearch snapshot provides a backup mechanism that takes the current state and data in the cluster and saves it to a repository (read snapshot for more information). The backup process requires a repository to be created first. The repository needs to be registered using the _snapshot endpoint, and multiple repositories can be created per cluster. The following repository types are supported:
Repository types
| Repository type | Configuration type |
|---|---|
| Shared file system | Type: “fs” |
| S3 | Type : “s3” |
| HDFS | Type :“hdfs” |
| Azure | Type: “azure” |
| Google Cloud Storage | Type : “gcs” |
Examples
To register an “fs” repository:
PUT _snapshot/my_repo_01
{
"type": "fs",
"settings": {
"location": "/mnt/my_repo_dir"
}
}Notes and good things to know
- S3, HDFS, Azure and Google Cloud require a relevant plugin to be installed before it can be used for a snapshot.
- The setting, path.repo: /mnt/my_repo_dir needs to be added to elasticsearch.yml on all the nodes if you are planning to use the repo type of file system. Otherwise, it will fail.
- When using remote repositories, the network bandwidth and repository storage throughput should be high enough to complete the snapshot operations normally, otherwise you will end up with partial snapshots.
Log Context
Log “Retrying broken resumable upload session for blob {}” classname is GoogleCloudStorageBlobStore.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
return;
} catch (final StorageException se) {
final int errorCode = se.getCode();
if (errorCode == HTTP_GONE) {
logger.warn(() -> new ParameterizedMessage("Retrying broken resumable upload session for blob {}"; blobInfo); se);
storageException = ExceptionsHelper.useOrSuppress(storageException; se);
continue;
} else if (failIfAlreadyExists && errorCode == HTTP_PRECON_FAILED) {
throw new FileAlreadyExistsException(blobInfo.getBlobId().getName(); null; se.getMessage());
}
[ratemypost]
