I'm using an ES 2.4.4.
Currently, I'm getting this content response at _cluster/health?level=nodes
{
"cluster_name":"logging-es",
"status":"red",
"timed_out":false,
"number_of_nodes":1,
"number_of_data_nodes":1,
"active_primary_shards":62,
"active_shards":62,
"relocating_shards":0,
"initializing_shards":0,
"unassigned_shards":2,
"delayed_unassigned_shards":0,
"number_of_pending_tasks":0,
"number_of_in_flight_fetch":0,
"task_max_waiting_in_queue_millis":0,
"active_shards_percent_as_number":96.875
}
As you can see, cluster has two shards unassigned: "unassigned_shards":2
.
Related indices are:
$ _cat/indices -s | grep red
red open project.istio-project-two.242ef609-8f... 1 0
red open project.3scale-amp-2.08baf3f... 1 0
These are the unassigned shards:
$ _cat/shards | grep UNASSIGNED
project.istio-project-two.242ef609-8f... 0 p UNASSIGNED
project.3scale-amp-2.08baf3f5-c3... 0 p UNASSIGNED
I don't know which is the reason ES is running in this issue.
Every day I delete these ones and then are created again. However, every day morning I need to apply this workaround I don't feel confortable.
The number of nodes:
$ _cat/nodes
10.128.2.21 10.128.2.21 67 99 0.41 d * logging-es-data-master-yl7ddqw7
Index settings:
$GET /project.istio-project-two.242ef609-8f/_settings?pretty
{
"project.istio-project-two.242ef609-8f..." : {
"settings" : {
"index" : {
"creation_date" : "1532649602432",
"refresh_interval" : "5s",
"number_of_shards" : "1",
"number_of_replicas" : "0",
"uuid" : "XY-tFCkhQVOLlXmndoKpSQ",
"version" : {
"created" : "2040499"
}
}
}
}
}
Any ideas?