.ds-.logs-deprecation.elasticsearch-default-* Unassigned Shards

[ng1991]

Recently I started monitoring the elastic via Zabbix and noticed we had quite a few unassigned shards for the deprecation logs, I was able to clear the back log but couldn't delete the most recent.

I first rolled the log over which allowed me to remove the faulty index but then the new log had the same issue. I then then noticed the cause was due to the index being created with number_of_replicas = 1.

If I change the value to 0 the unassigned shard is no longer there which makes sense

I am guessing this is an issue on the template used by the index but I am unsure on how best to change this.

Not a major issue but now i keep getting alerts when the file rolls over.

Any help would be appreciated

Thanks

[ng1991]

Hi this issue is still ongoing anyone any ideas?