Murmur3 fields are not searchable: ” + name() + ” – 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 ” Murmur3 fields are not searchable: ” + name() + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugins 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 “Murmur3 fields are not searchable: [” + name() + “]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return new DocValuesFieldExistsQuery(name());
 public Query termQuery(Object value; QueryShardContext context) {
 throw new QueryShardException(context; "Murmur3 fields are not searchable: [" + name() + "]");
 protected Murmur3FieldMapper(String simpleName; FieldType fieldType; MappedFieldType mappedFieldType;
 MultiFields multiFields; CopyTo copyTo) {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content