2013-08-28 19:24:34 -04:00
|
|
|
[[cluster]]
|
|
|
|
|
= Cluster APIs
|
|
|
|
|
|
|
|
|
|
[partintro]
|
|
|
|
|
--
|
|
|
|
|
["float",id="cluster-nodes"]
|
2013-10-13 10:46:56 -04:00
|
|
|
== Node specification
|
2013-08-28 19:24:34 -04:00
|
|
|
|
|
|
|
|
Most cluster level APIs allow to specify which nodes to execute on (for
|
|
|
|
|
example, getting the node stats for a node). Nodes can be identified in
|
|
|
|
|
the APIs either using their internal node id, the node name, address,
|
|
|
|
|
custom attributes, or just the `_local` node receiving the request. For
|
|
|
|
|
example, here are some sample executions of nodes info:
|
|
|
|
|
|
|
|
|
|
[source,js]
|
|
|
|
|
--------------------------------------------------
|
2013-10-13 10:46:56 -04:00
|
|
|
# Local
|
2013-08-28 19:24:34 -04:00
|
|
|
curl localhost:9200/_cluster/nodes/_local
|
|
|
|
|
# Address
|
|
|
|
|
curl localhost:9200/_cluster/nodes/10.0.0.3,10.0.0.4
|
|
|
|
|
curl localhost:9200/_cluster/nodes/10.0.0.*
|
|
|
|
|
# Names
|
|
|
|
|
curl localhost:9200/_cluster/nodes/node_name_goes_here
|
|
|
|
|
curl localhost:9200/_cluster/nodes/node_name_goes_*
|
|
|
|
|
# Attributes (set something like node.rack: 2 in the config)
|
|
|
|
|
curl localhost:9200/_cluster/nodes/rack:2
|
|
|
|
|
curl localhost:9200/_cluster/nodes/ra*:2
|
|
|
|
|
curl localhost:9200/_cluster/nodes/ra*:2*
|
|
|
|
|
--------------------------------------------------
|
|
|
|
|
--
|
|
|
|
|
|
|
|
|
|
include::cluster/health.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::cluster/state.asciidoc[]
|
|
|
|
|
|
2013-11-29 02:21:26 -05:00
|
|
|
include::cluster/pending.asciidoc[]
|
|
|
|
|
|
2013-08-28 19:24:34 -04:00
|
|
|
include::cluster/reroute.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::cluster/update-settings.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::cluster/nodes-stats.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::cluster/nodes-info.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::cluster/nodes-hot-threads.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::cluster/nodes-shutdown.asciidoc[]
|
