ILM Shrink - All primary on same node fails

Elastic Stack Elasticsearch
1

Hi All,

I'm using ILM-Policies in order to automate the Index-Lifecycle. As part of the Warm-Phase indices should be shrinked.
I'm currently running into the following problem reported by: GET /_cluster/allocation/explain:

{
  "decider" : "same_shard",
  "decision" : "NO",
  "explanation" : "a copy of this shard is already allocated to this node [[my-index-name-000002][4], node[1vFhysSMQEack-XZvmKkRg], [P], s[STARTED], a[id=1tF5F8jtTx-YNvcRYGSFOg]]"
}

The shrink action requires that all primary shards are assigned to the same node, but the same_node decider prevents that all primary shards are assigned to this node, as one of the replicas is already running on this node.

This finally stops the automated ILM / Shrink process. Any idea how to improve that? The ultimate goal is to avoid manual intervention into that process.

Thanks!
Chris

2

What's the output of _cat/allocation/my-index-name-000002?v?

3

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