Setting must be non-negative”; SHARED_CACHE_SETTINGS_PREFIX + “size – 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”; SHARED_CACHE_SETTINGS_PREFIX + “size ” 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”; SHARED_CACHE_SETTINGS_PREFIX + “size”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public void validate(final RelativeByteSizeValue value; final Map; Object> settings) {
 if (value.isAbsolute() && value.getAbsolute().getBytes() == -1) {
 throw new SettingsException("setting [{}] must be non-negative"; SHARED_CACHE_SETTINGS_PREFIX + "size");
 if (value.isNonZeroSize()) {
 final List roles = (List) settings.get(NodeRoleSettings.NODE_ROLES_SETTING);
 if (DataTier.isFrozenNode(Set.of(roles.toArray(DiscoveryNodeRole[]::new))) == false) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content