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

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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Index blob is not valid x-content bytes ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: blobstore, index, repositories and repository-azure.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “[{}] index blob is not valid x-content [{} bytes]” classname is BlobStoreRepository.java.
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




 

Run the Check-Up to get a customized report like this:

Analyze your cluster