Cluster state APIedit

Returns metadata about the state of the cluster.


GET /_cluster/state/<metrics>/<target>


The cluster state API allows access to metadata representing the state of the whole cluster. This includes information such as

  • the set of nodes in the cluster
  • all cluster-level settings
  • information about the indices in the cluster, including their mappings and settings
  • the locations of all the shards in the cluster.

The response is an internal representation of the cluster state and its format may change from version to version. If possible, you should obtain any information from the cluster state using the other, more stable, cluster APIs.

The response provides the cluster state itself, which can be filtered to only retrieve the parts of interest as described below.

The cluster’s cluster_uuid is also returned as part of the top-level response, in addition to the metadata section. [6.4.0] Added in 6.4.0.

While the cluster is still forming, it is possible for the cluster_uuid to be _na_ as well as the cluster state’s version to be -1.

By default, the cluster state request is routed to the master node, to ensure that the latest cluster state is returned. For debugging purposes, you can retrieve the cluster state local to a particular node by adding local=true to the query string.

Path parametersedit

The cluster state contains information about all the indices in the cluster, including their mappings, as well as templates and other metadata. This means it can sometimes be quite large. To avoid the need to process all this information you can request only the part of the cluster state that you need:


(Optional, string) A comma-separated list of the following options:

Shows all metrics.
Shows the blocks part of the response.
Shows the elected master_node part of the response.
Shows the metadata part of the response. If you supply a comma separated list of indices, the returned output will only contain metadata for these indices.
Shows the nodes part of the response.
Shows the routing_nodes part of the response.
Shows the routing_table part of the response. If you supply a comma separated list of indices, the returned output will only contain the routing table for these indices.
Shows the cluster state version.

(Optional, string) Comma-separated list of data streams, indices, and index aliases used to limit the request. Wildcard expressions (*) are supported.

To target all data streams and indices in a cluster, omit this parameter or use _all or *.

Query parametersedit


(Optional, boolean) If true, the wildcard indices expression that resolves into no concrete indices will be ignored. (This includes _all string or when no indices have been specified).

Defaults to true.

(Optional, string) Whether to expand wildcard expression to concrete indices that are open, closed or both. Available options: open, closed, none, all.
(Optional, boolean) If true, returns settings in flat format. Defaults to false.
(Optional, boolean) If true, unavailable indices (missing or closed) will be ignored.
(Optional, boolean) If true, the request retrieves information from the local node only. Defaults to false, which means information is retrieved from the master node.
(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.
(Optional, integer) Waits for the metadata version to be equal or greater than the specified metadata version.
(Optional, time units) Specifies the maximum time to wait for wait_for_metadata_version before timing out.


The following example returns only metadata and routing_table data for the foo and bar data streams or indices:

GET /_cluster/state/metadata,routing_table/foo,bar

The next example returns all available metadata for foo and bar:

GET /_cluster/state/_all/foo,bar

This example returns only the blocks metadata:

GET /_cluster/state/blocks