How to check Elasticsearch cluster health

Question

I tried to check it via   curl -XGET  http   localhost 9200  cluster health    but nothing happened  Seems it s waiting for something  The console did not come back  Had to kill it with CTRL C   I also tried to check for existing indices via  curl -XGET  http   localhost 9200  cat indices v    Same behavior as above

User · Answer

You can check elasticsearch cluster health by using (CURL) and Cluster API provieded by elasticsearch:

$ curl -XGET 'localhost:9200/_cluster/health?pretty'

This will give you the status and other related data you need.

{
 "cluster_name" : "xxxxxxxx",
 "status" : "green",
 "timed_out" : false,
 "number_of_nodes" : 2,
 "number_of_data_nodes" : 2,
 "active_primary_shards" : 15,
 "active_shards" : 12,
 "relocating_shards" : 0,
 "initializing_shards" : 0,
 "unassigned_shards" : 0,
 "delayed_unassigned_shards" : 0,
 "number_of_pending_tasks" : 0,
 "number_of_in_flight_fetch" : 0
}

User · Answer

The  cluster health API can do far more than the typical output that most see with it      curl -XGET  localhost 9200  cluster health pretty    Most APIs within Elasticsearch can take a variety of arguments to augment their output  This applies to Cluster Health API as well   Examples  all the indices health    curl -XGET  localhost 9200  cluster health level indices amp pretty    head -50      cluster name     rdu-es-01      status     green      timed out    false     number of nodes    9     number of data nodes    6     active primary shards    1106     active shards    2213     relocating shards    0     initializing shards    0     unassigned shards    0     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    100 0     indices           filebeat-6 5 1-2019 06 10             status     green          number of shards    3         number of replicas    1         active primary shards    3         active shards    6         relocating shards    0         initializing shards    0         unassigned shards    0             filebeat-6 5 1-2019 06 11             status     green          number of shards    3         number of replicas    1         active primary shards    3         active shards    6         relocating shards    0         initializing shards    0         unassigned shards    0             filebeat-6 5 1-2019 06 12             status     green          number of shards    3         number of replicas    1         active primary shards    3         active shards    6         relocating shards    0         initializing shards    0         unassigned shards    0             filebeat-6 5 1-2019 06 13             status     green          number of shards    3    all shards health    curl -XGET  localhost 9200  cluster health level shards amp pretty    head -50      cluster name     rdu-es-01      status     green      timed out    false     number of nodes    9     number of data nodes    6     active primary shards    1106     active shards    2213     relocating shards    0     initializing shards    0     unassigned shards    0     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    100 0     indices           filebeat-6 5 1-2019 06 10             status     green          number of shards    3         number of replicas    1         active primary shards    3         active shards    6         relocating shards    0         initializing shards    0         unassigned shards    0         shards               0                 status     green              primary active    true             active shards    2             relocating shards    0             initializing shards    0             unassigned shards    0                     1                 status     green              primary active    true             active shards    2             relocating shards    0             initializing shards    0             unassigned shards    0                     2                 status     green              primary active    true             active shards    2             relocating shards    0             initializing shards    0             unassigned shards    0   The API also has a variety of wait   options where it ll wait for various state changes before returning immediately or after some specified timeout

User · Answer

If Elasticsearch cluster is not accessible  e g  behind firewall   but Kibana is  Kibana   gt  DevTools   gt  Console  GET   cluster health

User · Answer

To check on elasticsearch cluster health you need to use  curl localhost 9200  cat health   More on the cat APIs here   I usually use elasticsearch-head plugin to visualize that   You can find it s github project here   It s easy to install sudo  ES HOME bin plugin -i mobz elasticsearch-head and then you can open localhost 9200  plugin head  in your web brower   You should have something that looks like this

User · Answer

PROBLEM  -  Sometimes  Localhost may not get resolved  So it tends to return an output as seen below      curl -XGET localhost 9200  cluster health pretty   lt  DOCTYPE html PUBLIC  -  W3C  DTD HTML 4 01  EN   http   www w3 org TR html4 strict dtd  gt   lt html gt  lt head gt   lt meta http-equiv  Content-Type  CONTENT  text html  charset iso-8859-1  gt   lt title gt ERROR  The requested URL could not be retrieved lt  title gt   lt style type  text css  gt  lt  --BODY background-color  ffffff font-family verdana sans-serif PRE font-family sans-serif -- gt  lt  style gt   lt  head gt  lt body gt   lt h1 gt ERROR lt  h1 gt   lt h2 gt The requested URL could not be retrieved lt  h2 gt   lt hr gt   lt p gt The following error was encountered while trying to retrieve the URL   lt a href  http   localhost 9200  cluster health   gt http   localhost 9200  cluster health  lt  a gt  lt  p gt   lt blockquote gt   lt p gt  lt b gt Connection to 127 0 0 1 failed  lt  b gt  lt  p gt   lt  blockquote gt    lt p gt The system returned   lt i gt  111  Connection refused lt  i gt  lt  p gt    lt p gt The remote host or network may be down   Please try the request again  lt  p gt   lt p gt Your cache administrator is  lt a href  mailto root subject CacheErrorInfo 20- 20ERR CONNECT FAIL amp amp body CacheHost 3A 20squid2 0D 0AErrPage 3A 20ERR CONNECT FAIL 0D 0AErr 3A 20 111  20Connection 20refused 0D 0ATimeStamp 3A 20Mon  2017 20Dec 202018 2008 3A07 3A36 20GMT 0D 0A 0D 0AClientIP 3A 20192 168 13 14 0D 0AServerIP 3A 20127 0 0 1 0D 0A 0D 0AHTTP 20Request 3A 0D 0AGET 20 2F cluster 2Fhealth 3Fpretty 20HTTP 2F1 1 0AUser-Agent 3A 20curl 2F7 29 0 0D 0AHost 3A 20localhost 3A9200 0D 0AAccept 3A 20  2F  0D 0AProxy-Connection 3A 20Keep-Alive 0D 0A 0D 0A 0D 0A  gt root lt  a gt   lt  p gt    lt br gt      lt hr gt    lt div id  footer  gt Generated Mon  17 Dec 2018 08 07 36 GMT by squid2  squid 3 0 STABLE25  lt  div gt   lt  body gt  lt  html gt      curl -XGET localhost 9200  cat indices   lt  DOCTYPE html PUBLIC  -  W3C  DTD HTML 4 01  EN   http   www w3 org TR html4 strict dtd  gt   lt html gt  lt head gt   lt meta http-equiv  Content-Type  CONTENT  text html  charset iso-8859-1  gt   lt title gt ERROR  The requested URL could not be retrieved lt  title gt   lt style type  text css  gt  lt  --BODY background-color  ffffff font-family verdana sans-serif PRE font-family sans-serif -- gt  lt  style gt   lt  head gt  lt body gt   lt h1 gt ERROR lt  h1 gt   lt h2 gt The requested URL could not be retrieved lt  h2 gt   lt hr gt   lt p gt The following error was encountered while trying to retrieve the URL   lt a href  http   localhost 9200  cat indices  gt http   localhost 9200  cat indices lt  a gt  lt  p gt   lt blockquote gt   lt p gt  lt b gt Connection to 127 0 0 1 failed  lt  b gt  lt  p gt   lt  blockquote gt    lt p gt The system returned   lt i gt  111  Connection refused lt  i gt  lt  p gt    lt p gt The remote host or network may be down   Please try the request again  lt  p gt   lt p gt Your cache administrator is  lt a href  mailto root subject CacheErrorInfo 20- 20ERR CONNECT FAIL amp amp body CacheHost 3A 20squid2 0D 0AErrPage 3A 20ERR CONNECT FAIL 0D 0AErr 3A 20 111  20Connection 20refused 0D 0ATimeStamp 3A 20Mon  2017 20Dec 202018 2008 3A10 3A09 20GMT 0D 0A 0D 0AClientIP 3A 20192 168 13 14 0D 0AServerIP 3A 20127 0 0 1 0D 0A 0D 0AHTTP 20Request 3A 0D 0AGET 20 2F cat 2Findices 20HTTP 2F1 1 0AUser-Agent 3A 20curl 2F7 29 0 0D 0AHost 3A 20localhost 3A9200 0D 0AAccept 3A 20  2F  0D 0AProxy-Connection 3A 20Keep-Alive 0D 0A 0D 0A 0D 0A  gt root lt  a gt   lt  p gt    lt br gt      lt hr gt    lt div id  footer  gt Generated Mon  17 Dec 2018 08 10 09 GMT by squid2  squid 3 0 STABLE25  lt  div gt   lt  body gt  lt  html gt    SOLUTION  -  Guess  this error is most probably returned by Local Squid deployed in the server   So  it worked fine and good after replacing localhost by the local ip in which the ElasticSearch has been deployed

[elasticsearch] How to check Elasticsearch cluster health?

Examples related to elasticsearch