Too errorPrefix lowerCase length > 36 long short – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when the length of a string in Elasticsearch is either too long or too short. The error message indicates that the string length exceeds 36 characters or is less than the required minimum. To resolve this issue, you can adjust the string length to meet the required criteria. If the string is too long, you can truncate it or split it into smaller parts. If it’s too short, you can append additional characters or combine it with other strings to meet the minimum length requirement.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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, plugin.

Log Context

Log “{}too {}”; errorPrefix; lowerCase.length() > 36 ? “long” : “short” class name 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) != '-') {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?