Missing or invalid physical file name ” + physicalName + ” – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” missing or invalid physical file name ” + physicalName + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore and index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

// Verify that file information is complete
 if (name == null || Strings.validFileName(name) == false) {
 throw new ElasticsearchParseException("missing or invalid file name [" + name + "]");
 } 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) {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content