Failed to parse int 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 convert a setting’s value into an integer. This could be due to the setting’s value being a non-integer or a string that cannot be parsed into an integer. To resolve this issue, you should check the setting’s value and ensure it is an integer. If it’s a string, make sure it can be parsed into an integer. If the setting doesn’t require an integer value, you may need to adjust the code or configuration that requires it to be an integer.

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 int 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.

Log Context

Log “Failed to parse int 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 Integer.parseInt(sValue);
 } catch (NumberFormatException e) {
 throw new SettingsException("Failed to parse int setting [" + setting + "] with value [" + sValue + "]"; e);
 }  /**
 * Returns the setting value (as long) associated with the setting key. If it does not exists;


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