Retrying broken resumable upload session for blob – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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: cloud-aws, plugins, repositories, repository-gcs and storage.

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());


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content