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

Opster Team

August-23, Version: 7.14-8.9

Briefly, this error occurs when the “written_by” field in an Elasticsearch document is either missing or contains invalid data. This could be due to incorrect data input or a missing field in the document schema. To resolve this issue, you can: 1) Check the data being inputted to ensure it is valid and correctly formatted. 2) Verify that the “written_by” field exists in your document schema. 3) If the field is optional, modify your code to handle cases where it might be missing. 4) If the field is mandatory, ensure all documents contain this field before indexing.

This guide will help you check for common problems that cause the log ” missing or invalid written_by [” + writtenBy + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, index.

Log Context

Log “missing or invalid written_by [” + writtenBy + “]” 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 [" + writtenBy + "]");
 } else if (checksum == null) {
 throw new ElasticsearchParseException("missing checksum for name [" + name + "]");
 return new FileInfo(name; new StoreFileMetadata(physicalName; length; checksum; writtenBy; metaHash; writerUuid); 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?