Too “; errorPrefix; lowerCase.length() > 36 ? “long” : “short – 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.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” too “; errorPrefix; lowerCase.length() > 36 ? “long” : “short ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: parser and plugin.

Log Context

Log “{}too {}”; errorPrefix; lowerCase.length() > 36 ? “long” : “short”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// not pretty but it's fast and doesn't create any extra objects 
 String errorPrefix = "Invalid GUID; "; 
 if (lowerCase.length() != 36) {
 throw new ParsingException(source; "{}too {}"; errorPrefix; lowerCase.length() > 36 ? "long" : "short");
 int[] separatorPos = { 8; 13; 18; 23 };
 for (int pos : separatorPos) {
 if (lowerCase.charAt(pos) != '-') {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content