Cluster health APIedit
Returns the health status of a cluster.
Requestedit
GET _cluster/health/<index>
Descriptionedit
The cluster health API returns a simple status on the health of the cluster. The API can also be executed against one or more indices to get just the specified indices health.
The cluster health status is: green, yellow or red. On the shard level, a
red status indicates that the specific shard is not allocated in the cluster,
yellow means that the primary shard is allocated but replicas are not, and
green means that all shards are allocated. The index level status is
controlled by the worst shard status. The cluster status is controlled by the
worst index status.
One of the main benefits of the API is the ability to wait until the cluster
reaches a certain high water-mark health level. For example, the following will
wait for 50 seconds for the cluster to reach the yellow level (if it reaches
the green or yellow status before 50 seconds elapse, it will return at that
point):
GET /_cluster/health?wait_for_status=yellow&timeout=50s
Path parametersedit
-
<index> - (Optional, string) Comma-separated list or wildcard expression of index names used to limit the request.
Query parametersedit
-
level -
(Optional, string) Can be one of
cluster,indicesorshards. Controls the details level of the health information returned. Defaults tocluster. -
local -
(Optional, boolean) If
true, the request retrieves information from the local node only. Defaults tofalse, which means information is retrieved from the master node. -
master_timeout -
(Optional, time units) Specifies the period of time to wait for
a connection to the master node. If no response is received before the timeout
expires, the request fails and returns an error. Defaults to
30s. -
timeout -
(Optional, time units) Specifies the period of time to wait for
a response. If no response is received before the timeout expires, the request
fails and returns an error. Defaults to
30s. -
wait_for_active_shards -
(Optional, string) A number controlling to how many active shards to wait
for,
allto wait for all shards in the cluster to be active, or0to not wait. Defaults to0. -
wait_for_events -
(Optional, string) Can be one of
immediate,urgent,high,normal,low,languid. Wait until all currently queued events with the given priority are processed. -
wait_for_no_initializing_shards - (Optional, boolean) A boolean value which controls whether to wait (until the timeout provided) for the cluster to have no shard initializations. Defaults to false, which means it will not wait for initializing shards.
-
wait_for_no_relocating_shards - (Optional, boolean) A boolean value which controls whether to wait (until the timeout provided) for the cluster to have no shard relocations. Defaults to false, which means it will not wait for relocating shards.
-
wait_for_nodes -
(Optional, string) The request waits until the specified number
Nof nodes is available. It also accepts>=N,<=N,>Nand<N. Alternatively, it is possible to usege(N),le(N),gt(N)andlt(N)notation. -
wait_for_status -
(Optional, string) One of
green,yelloworred. Will wait (until the timeout provided) until the status of the cluster changes to the one provided or better, i.e.green>yellow>red. By default, will not wait for any status.
Response bodyedit
-
cluster_name - (string) The name of the cluster.
-
status -
(string) Health status of the cluster, based on the state of its primary and replica shards. Statuses are:
-
green - All shards are assigned.
-
yellow - All primary shards are assigned, but one or more replica shards are unassigned. If a node in the cluster fails, some data could be unavailable until that node is repaired.
-
red - One or more primary shards are unassigned, so some data is unavailable. This can occur briefly during cluster startup as primary shards are assigned.
-
-
timed_out -
(boolean) If
falsethe response returned within the period of time that is specified by thetimeoutparameter (30sby default). -
number_of_nodes - (integer) The number of nodes within the cluster.
-
number_of_data_nodes - (integer) The number of nodes that are dedicated data nodes.
-
active_primary_shards - (integer) The number of active primary shards.
-
active_shards - (integer) The total number of active primary and replica shards.
-
relocating_shards - (integer) The number of shards that are under relocation.
-
initializing_shards - (integer) The number of shards that are under initialization.
-
unassigned_shards - (integer) The number of shards that are not allocated.
-
delayed_unassigned_shards - (integer) The number of shards whose allocation has been delayed by the timeout settings.
-
number_of_pending_tasks - (integer) The number of cluster-level changes that have not yet been executed.
-
number_of_in_flight_fetch - (integer) The number of unfinished fetches.
-
task_max_waiting_in_queue_millis - (integer) The time expressed in milliseconds since the earliest initiated task is waiting for being performed.
-
active_shards_percent_as_number - (float) The ratio of active shards in the cluster expressed as a percentage.
Examplesedit
GET _cluster/health
The API returns the following response in case of a quiet single node cluster with a single index with one shard and one replica:
{
"cluster_name" : "testcluster",
"status" : "yellow",
"timed_out" : false,
"number_of_nodes" : 1,
"number_of_data_nodes" : 1,
"active_primary_shards" : 1,
"active_shards" : 1,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 1,
"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": 50.0
}
The following is an example of getting the cluster health at the
shards level:
GET /_cluster/health/twitter?level=shards