Setting is set but and are not – How to solve this Elasticsearch error

Average Read Time

2 Mins

Setting is set but and are not – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Setting is set but and are not ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: discovery-ec2, plugins and discovery.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”Setting [{}] is set but [{}] and [{}] are not”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

try (SecureString key = ACCESS_KEY_SETTING.get(settings);
  SecureString secret = SECRET_KEY_SETTING.get(settings);
  SecureString sessionToken = SESSION_TOKEN_SETTING.get(settings)) {
  if (key.length() == 0 && secret.length() == 0) {
  if (sessionToken.length() > 0) {
  throw new SettingsException("Setting [{}] is set but [{}] and [{}] are not";
  logger.debug("Using either environment variables; system properties or instance profile credentials");
  return null;


Run the Check-Up to get a customized report like this:

Analyze your cluster