Author: past Memory | Sina Weibo: Left hand in the right hand tel | Can be reproduced, but must be in the form of hyperlinks to indicate the original source of the article and author information and copyright notice
Blog Address: http://www.iteblog.com/
Article title: Introduction to the rest API for Web services in Hadoop yarn
This article link: http://www.iteblog.com/archives/960
Hadoop, Hive, Hbase, Flume, such as QQ Exchange Group: 138615359
Hadoop Yarn has a series of Web service REST APIs that we can use to access the cluster (cluster), nodes (nodes), Applications (application), and historical information for the application. Depending on the type returned by the API, these URL sources are grouped into different groups. Some APIs return collector types, and some return singleton types. The syntax for these Web service REST APIs is as follows:
1 |
http://{http address of Service}/ws/{version}/{resourcepath} |
where {HTTP address of service} is the server where we need to get information, currently supports access to ResourceManager, Nodemanager,mapreduce application master, and History Server;{version} is the version of these APIs, and currently supports only V1;{resourcepath} to define the path to singleton or collection resources.
Here are examples of how these Web service uses.
Suppose you have a application_1388830974669_1540349 job and run out of it. You can get some information about this job by using the following command:
1 2 |
$ Curl--compressed-h "Accept:application/json"-X \ Get "Http://host.domain.com:8088/ws/v1/cluster/apps/application_ 1326821518301_0010 " |
The results of the above run are returned in a JSON format, as follows: