Missing or invalid written by writtenByStr – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.13

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 Elasticsearch operation.

Briefly, this error occurs when Elasticsearch cannot find or validate the “written_by” field. This could be due to the field being absent, misspelled, or containing invalid data. To resolve this issue, you can check the data being indexed to ensure the “written_by” field is present and correctly spelled. Also, validate the data in the “written_by” field to ensure it meets the expected format or data type. If you’re using a script or automated process to index data, ensure it’s correctly configured to include and properly format this field.

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 ” missing or invalid written_by [” + writtenByStr + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, blobstore.

Log Context

Log “missing or invalid written_by [” + writtenByStr + “]” class name is BlobStoreIndexShardSnapshot.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else if (physicalName == null || Strings.validFileName(physicalName) == false) {
 throw new ElasticsearchParseException("missing or invalid physical file name [" + physicalName + "]");
 } else if (length < 0) {
 throw new ElasticsearchParseException("missing or invalid file length");
 } else if (writtenBy == null) {
 throw new ElasticsearchParseException("missing or invalid written_by [" + writtenByStr + "]");
 } else if (checksum == null) {
 throw new ElasticsearchParseException("missing checksum for name [" + name + "]");
 }
 return new FileInfo(name; new StoreFileMetadata(physicalName; length; checksum; writtenBy; metaHash); partSize);
 }

 

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?