Setting must be non-negative – How to solve this Elasticsearch error

Opster Team

March-22, 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 ” setting must be non-negative ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cache, plugin.

Log Context

Log “setting [{}] must be non-negative”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 private static Setting.Validator getPageSizeAlignedByteSizeValueValidator(String settingName) {
 return value -> {
 if (value.getBytes() == -1) {
 throw new SettingsException("setting [{}] must be non-negative"; settingName);
 if (value.getBytes() % SharedBytes.PAGE_SIZE != 0L) {
 throw new SettingsException("setting [{}] must be multiple of {}"; settingName; SharedBytes.PAGE_SIZE);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content