Kibana console showing Elastic Search as “Red” status & all shards failed error

Hi All,

I face error when i try to run kibana console from my virtual machine, screenshot attached for ref.

Also i checked the logs, i could see below lines which i'm completely not awarekibana_Status_Red .

[2019-06-18T11:19:17,974][DEBUG][o.e.a.s.TransportSearchAction] [elk-denmod-web] All shards failed for phase: [query]
org.elasticsearch.action.NoShardAvailableActionException: null
at ~[elasticsearch-5.3.1.jar:5.3.1]
at ~[elasticsearch-5.3.1.jar:5.3.1]
at ~[elasticsearch-5.3.1.jar:5.3.1]
at ~[elasticsearch-5.3.1.jar:5.3.1]
at$RequestFilterChain.proceed( ~[elasticsearch-5.3.1.jar:5.3.1]
at ~[elasticsearch-5.3.1.jar:5.3.1]
at ~[elasticsearch-5.3.1.jar:5.3.1]
at org.elasticsearch.client.node.NodeClient.executeLocally( ~[elasticsearch-5.3.1.jar:5.3.1]
at org.elasticsearch.client.node.NodeClient.doExecute( ~[elasticsearch-5.3.1.jar:5.3.1]
at ~[elasticsearch-5.3.1.jar:5.3.1]
at ~[elasticsearch-5.3.1.jar:5.3.1]
at$prepareRequest$1( ~[elasticsearch-5.3.1.jar:5.3.1]
at [elasticsearch-5.3.1.jar:5.3.1]
at [elasticsearch-5.3.1.jar:5.3.1]
at [elasticsearch-5.3.1.jar:5.3.1]
at org.elasticsearch.http.netty4.Netty4HttpServerTransport.dispatchRequest( [transport-netty4-5.3.1.jar:5.3.1]
at org.elasticsearch.http.netty4.Netty4HttpRequestHandler.channelRead0( [transport-netty4-5.3.1.jar:5.3.1]
at [netty-transport-4.1.7.Final.jar:4.1.7.Final]
at [netty-transport-4.1.7.Final.jar:4.1.7.Final]
at [netty-transport-4.1.7.Final.jar:4.1.7.Final]

Please let me know , what i need to do to resolve this issue.

Thanks in advance.

This is the health output got from the url : http://localhost:9200/_cluster/health?pretty

"cluster_name" : "elk-denmod",
"status" : "yellow",
"timed_out" : false,
"number_of_nodes" : 1,
"number_of_data_nodes" : 0,
"active_primary_shards" : 0,
"active_shards" : 0,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 24,
"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" : 0.0

Hi Joseph,
try this:

GET /_cluster/allocation/explain

This can be helpful:

1 Like

As you can see from the health check, your cluster has no data nodes.

You will either have to set true on the one node you have or add a dedicated data node to your cluster. Otherwise Elasticsearch will have nowhere to assign the 24 unassigned shards you currently have in the cluster.

1 Like

where do i need to run this line of code ?
as im new to this, im not aware.
Please help

Even if i change the node status to true, still it shows as red.

Did you restart Elasticsearch after setting true in the config/elasticsearch.yml file?

If you did, what does health tell you now? Is "number_of_data_nodes" 1 or still 0?

If you now have a data node in the cluster, the red health must be due to one or more red indices.

For example you can run command from:

1) Kibana
You can run command in Kibana - Dev Tools - Console.

2) Curl
You can use curl utility in command line

curl -XGET localhost:9200

Edit your elasticsearch.yml file located in the conf repo of Elasticsearch. Set true and restart your Elasticsearch instance

1 Like

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