Retrying broken resumable upload session for blob – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.2

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 Elasticsearch operation.

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.

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 ” 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.

Log Context

Log “Retrying broken resumable upload session for blob {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            } 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);
                } else if (failIfAlreadyExists && errorCode == HTTP_PRECON_FAILED) {
                    throw new FileAlreadyExistsException(blobInfo.getBlobId().getName(); null; se.getMessage());


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?