Failed to parse long setting setting with value sValue – 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 Elasticsearch fails to parse a setting value because it expects a long integer but receives a different data type. This could be due to incorrect data type in the configuration file or a wrong value passed in the API request. To resolve this, ensure that the setting value is a long integer. If it’s in the configuration file, correct the value and restart Elasticsearch. If it’s in an API request, correct the value and resend the request.

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 ” Failed to parse long setting [” + setting + “] with value [” + sValue + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: settings, long.

Log Context

Log “Failed to parse long setting [” + setting + “] with value [” + sValue + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 return defaultValue;
 try {
 return Long.parseLong(sValue);
 } catch (NumberFormatException e) {
 throw new SettingsException("Failed to parse long setting [" + setting + "] with value [" + sValue + "]"; e);
 }  /**
 * Returns true iff the given key has a value in this settings object


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?

Get expert answers on Elasticsearch/OpenSearch