Hello,
I understand why Elastic manages the primary and replica shards of enrich indices. I get that the whole point is parallelism, but the end user should be able to manage the shard settings. It is causing an imbalance because the elastic logic is applied.
Currently, the unassigned shards (all coming from enrich indices) are not being assigned because the nodes are reporting in _cluster/allocation/explain that every node already has a shard:
"explanation": "a copy of this shard is already allocated to this node [[.enrich-<redacted>][0], node[<redacted>], [R], s[STARTED], a[id=<redacted>], failed_attempts[0]]"
This are the default settings:
I ran this:
PUT .enrich-*/_settings {"index": {"number_of_replicas": 1}}
And did nothing because it’s not manageable by the end user.
ES version: 9.1.3