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

Opster Team

Aug-23, Version: 8.3-8.9

Briefly, this error occurs when Elasticsearch attempts to upload a blob to a storage system, but the upload session is interrupted or broken. This could be due to network issues, storage system failures, or other transient errors. To resolve this issue, you can try the following: 1) Check your network connection and ensure it’s stable. 2) Verify the storage system is functioning properly. 3) Increase the timeout settings in Elasticsearch. 4) If the problem persists, consider breaking the blob into smaller chunks for upload.

This guide will help you check for common problems that cause the log ” Retrying broken resumable upload session for blob %s ” 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 %s” 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(() -> format("Retrying broken resumable upload session for blob %s"; 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?