Unassigned shard in "nagioslogserver_history" index
Posted: Thu Feb 29, 2024 12:41 pm
I have a single-instance deployment of v2.1.15. After setting up alerts, I noticed that the cluster status went from "green" to "yellow." This appears to be due to an unassigned shard in the "nagioslogserver_history" index. Trimming the index resets the cluster status to green, but it reverts to yellow as soon as an alert runs. Any thoughts on why this is happening?
"nagioslogserver_history" : {
"status" : "yellow",
"number_of_shards" : 1,
"number_of_replicas" : 1,
"active_primary_shards" : 1,
"active_shards" : 1,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 1
"nagioslogserver_history" : {
"status" : "yellow",
"number_of_shards" : 1,
"number_of_replicas" : 1,
"active_primary_shards" : 1,
"active_shards" : 1,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 1