Expected: ” + RPAREN + ” but found: – How to solve this Elasticsearch error

Expected: ” + RPAREN + ” 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 Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” expected: ” + RPAREN + ” but found: ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: Node.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”expected: [{}]” + RPAREN + ” but found: [{}]”classname  is GeoWKTParser.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (isNumberNext(stream) || (isOpenParen = nextWord(stream).equals(LPAREN))) {
  coordinates.coordinate(parseCoordinate(stream; ignoreZValue; coerce));
  if (isOpenParen && nextCloser(stream).equals(RPAREN) == false) {
  throw new ElasticsearchParseException("expected: [{}]" + RPAREN + " but found: [{}]" + tokenString(stream); stream.lineno());
  while (nextCloserOrComma(stream).equals(COMMA)) {
  isOpenParen = false;
  if (isNumberNext(stream) || (isOpenParen = nextWord(stream).equals(LPAREN))) {


Run the Check-Up to get a customized report like this:

Analyze your cluster