Expected word but found: – 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 ” expected word but found: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Node.

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 “expected word but found:”classname  is GeoWKTParser.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return word.equalsIgnoreCase(EMPTY) ? EMPTY : word;
 case '(': return LPAREN;
 case ')': return RPAREN;
 case ';': return COMMA;
 throw new ElasticsearchParseException("expected word but found: " + tokenString(stream); stream.lineno());
 private static double nextNumber(StreamTokenizer stream) throws IOException; ElasticsearchParseException {
 if (stream.nextToken() == StreamTokenizer.TT_WORD) {
 if (stream.sval.equalsIgnoreCase(NAN)) {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content