Expected ” + EMPTY + ” or – 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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” expected ” + EMPTY + ” or ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Node.

Log Context

Log “expected ” + EMPTY + ” or”classname  is GeoWKTParser.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

private static String nextEmptyOrOpen(StreamTokenizer stream) throws IOException; ElasticsearchParseException {
 final String next = nextWord(stream);
 if (next.equals(EMPTY) || next.equals(LPAREN)) {
 return next;
 throw new ElasticsearchParseException("expected " + EMPTY + " or " + LPAREN
 + " but found: " + tokenString(stream); stream.lineno());
 private static String nextCloser(StreamTokenizer stream) throws IOException; ElasticsearchParseException {
 if (nextWord(stream).equals(RPAREN)) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content