Shard allocation for master nodes during rolling upgrades

Elastic Stack Elasticsearch
1

I'm aware that shard allocation needs to be disabled and then re-enabled back during rolling upgrades.

My question is: Does this need to be done for master nodes?

I reckon this is only needed for data nodes and NOT needed for master nodes. Can someone confirm? The main purpose of disabling and enabling is to prevent un-necessary movement of shards across nodes but master nodes don't contain any shards in first place.

2

Shard allocation is disabled with a cluster-wide setting:

PUT _cluster/settings
{
  "transient": {
    "cluster.routing.allocation.enable": "none"
  }
}

It doesn't make sense to talk about disabling it only on some nodes.

3

Hi David,

Thanks for your answer. I am aware it's a cluster level setting. The first point of rolling upgrades asks to disable shard allocation and my question was whether this needs to be done for upgrading/restarting of master nodes? because a master node doesn't contain any shards in first place and so I was wondering if we can skip disabling and enabling of shard allocation when we are doing rolling upgrade on master nodes. Got my point?

IMHO, the disabling and enabling of shard allocation steps are moot for master nodes. Even though the setting is at cluster level, it needs to be done only when restarting/upgrading data nodes. This i what I understand and was looking to confirm if my understanding is correct or not.

4

I see, sorry, I misunderstood your question. Yes, disabling shard allocation is only really meaningful when restarting a data node.

5

Thank you David.

6

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