Elastic cluster, auto-adds/resets new nodes into shard exclusion list

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

Hi All,
Whenever I add a scale up my Elastic cluster through GCP console, I see my nodes getting added into cluster allocation exclusion list. Like:

GET _cluster/settings
"transient" : {
    "cluster" : {
      "routing" : {
        "rebalance" : {
          "enable" : "all"
        },
        "allocation" : {
          "allow_rebalance" : "always",
          "exclude" : {
            "_name" : "master-pool-3,warm-pool-12,warm-pool-11,es-warm-pool-10,es-warm-pool-9",
          },
          "node_initial_primaries_recoveries" : "40",
          "enable" : "all"
        }
      }
    }
  }

Even if I reset the value the below request, the settings automatically resets:

PUT _cluster/settings
{
"transient" : {
    "cluster" : {
      "routing" : {
        "allocation" : {
            "_name" : "none_excluded",
            "_ip" : null
        }
      }
    }
  }
}

Any pointers is well appreciated.

2

Welcome to our community! :smiley:

Are you using our Elasticsearch Service?

3

Hi, We are using ECK operator on GKE

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.