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

Opster Team

Aug-23, Version: 1-2.9

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 is trying to upload data to a blob storage and the upload session breaks or interrupts. This could be due to network issues, storage limitations, or problems with the blob storage service. To resolve this, you can try to ensure a stable network connection, increase storage capacity, or check the health of the blob storage service. If the problem persists, consider breaking the data into smaller chunks for upload or using a different blob storage service.

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 OpenSearch concepts: repositories, repository-gcs, plugins.

Log Context

Log “Retrying broken resumable upload session for blob {}” classname is
We extracted the following from OpenSearch 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?

Get expert answers on Elasticsearch/OpenSearch