Index blob is not valid x-content bytes – How to solve related issues

Opster Team

Jan-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. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Index blob is not valid x-content bytes ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, index, repositories and repository-azure.

Log Context

Log “[{}] index blob is not valid x-content [{} bytes]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 // EMPTY is safe here because RepositoryData#fromXContent calls namedObject
                try (XContentParser parser = XContentHelper.createParser(NamedXContentRegistry.EMPTY;
                    LoggingDeprecationHandler.INSTANCE; out.bytes(); XContentType.JSON)) {
                    repositoryData = RepositoryData.snapshotsFromXContent(parser; indexGen);
                } catch (NotXContentException e) {
                    logger.warn("[{}] index blob is not valid x-content [{} bytes]"; snapshotsIndexBlobName; out.bytes().length());
                    throw e;

            // now load the incompatible snapshot ids; if they exist


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content