2013-11-14 20:14:39 -05:00
|
|
|
[[cat-master]]
|
2014-05-16 15:43:35 -04:00
|
|
|
== cat master
|
2013-11-14 20:14:39 -05:00
|
|
|
|
|
|
|
|
`master` doesn't have any extra options. It simply displays the
|
|
|
|
|
master's node ID, bound IP address, and node name.
|
|
|
|
|
|
2015-07-14 12:14:09 -04:00
|
|
|
[source,sh]
|
2013-11-14 20:14:39 -05:00
|
|
|
--------------------------------------------------
|
2013-12-02 09:27:41 -05:00
|
|
|
% curl 'localhost:9200/_cat/master?v'
|
2013-11-14 20:14:39 -05:00
|
|
|
id ip node
|
|
|
|
|
Ntgn2DcuTjGuXlhKDUD4vA 192.168.56.30 Solarr
|
|
|
|
|
--------------------------------------------------
|
|
|
|
|
|
|
|
|
|
This information is also available via the `nodes` command, but this
|
|
|
|
|
is slightly shorter when all you want to do, for example, is verify
|
|
|
|
|
all nodes agree on the master:
|
|
|
|
|
|
2015-07-14 12:14:09 -04:00
|
|
|
[source,sh]
|
2013-11-14 20:14:39 -05:00
|
|
|
--------------------------------------------------
|
|
|
|
|
% pssh -i -h list.of.cluster.hosts curl -s localhost:9200/_cat/master
|
|
|
|
|
[1] 19:16:37 [SUCCESS] es3.vm
|
|
|
|
|
Ntgn2DcuTjGuXlhKDUD4vA 192.168.56.30 Solarr
|
|
|
|
|
[2] 19:16:37 [SUCCESS] es2.vm
|
|
|
|
|
Ntgn2DcuTjGuXlhKDUD4vA 192.168.56.30 Solarr
|
|
|
|
|
[3] 19:16:37 [SUCCESS] es1.vm
|
|
|
|
|
Ntgn2DcuTjGuXlhKDUD4vA 192.168.56.30 Solarr
|
|
|
|
|
--------------------------------------------------
|
