• MapReduce Service

  1. Help Center
  2. MapReduce Service
  3. API Reference
  4. MRS Manager APIs
  5. MRS Manager API Use Methods
  6. MRS Manager APIs

MRS Manager APIs

MRS Manager APIs are provided for you to query basic information about MRS clusters and monitoring status, as well as start and stop services.

MRS Manager APIs can be accessed only by nodes in the same VPC as the cluster.

Clusters with Kerberos authentication disabled can directly call MRS Manager APIs in the same VPC for access. However, clusters with Kerberos authentication enabled must obtain authentication information before calling MRS Manager APIs.

A MRS Manager API request or response consists of the following six parts:

Request URI

A request URI consists of the following parts:

{URI-scheme} :// {Floating IP address of MRS Manager}:{MRS Manager port} / {resource-path} ? {query-string}

Although the request URI is included in the request header, most languages or frameworks require that it be transmitted separately from the request message. Therefore, the request URI is listed independently.

Table 1 Parameters in a URI




Specifies the protocol used for transmitting requests. HTTPS must be used in MRS APIs.

Floating IP address of MRS Manager

IP address for logging in to MRS Manager

For a security cluster that supports Kerberos authentication, you can view the floating IP address in Cluster Manager IP Address on the basic cluster information page.

For a non-security cluster that does not support Kerberos authentication, you can log in to the Master2 node of the cluster using VNC and run the ifconfig command to view the floating IP address of the cluster. eth0:wsom indicates the floating IP address of MRS Manager. The value of the inet parameter is the floating IP address.


If the floating IP address of MRS Manager cannot be queried on the Master2 node, switch to the Master1 node to query and record the floating IP address.

MRS Manager port

Port for logging in to MRS Manager. The default value is 28443.


Specifies a resource path, that is, an API access path. Obtain this value from the URI of a specific API, for example, v3/auth/tokens.

Query string

This parameter is optional. For example, you can set it to API version or resource selection criteria.

Request Methods

HTTP methods, which are also called operations or actions, specify the type of operations that you are requesting.

Table 2 HTTP methods




Requests a server to return the specified resources.


Requests a server to update the specified resources.


Requests a server to add resources or perform special operations.


Requests a server to delete specified resources, for example, an object.


Requests a server resource header.


Requests a server to update the partial content of the specified resource.

If the resource does not exist, the PATCH method may create a resource.

Request Header

A request header consists of several header fields. Each header field consists of a field name, a colon (:), and a field value.

You can also add additional fields to the request header, for example, the fields required by a specified URI and an HTTP method. For details about common request headers, see Table 3. For details about the request authentication information, see Obtaining Request Authentication Information.

Table 3 Common request headers



Mandatory or Not



MIME type of the sent request body




Length of the request body. The unit is byte.

This parameter is mandatory for POST and PUT requests but must be left blank for GET requests.



Request language. Values include:

  • zh-cn: Chinese
  • en-us: English




For details about other parameters in the header, see the HTTP protocol documentation.

Request Body

A request body is generally sent in a structured format (for example, JSON or XML), corresponding to Content-type in the request header, and is used to transfer content other than the request header.

Response Header

A response header consists of the following two parts:

  • An HTTP status code, from 2xx success code to 4xx or 5xx error code, or status code that can return the service definition, as shown in the API document
  • Additional fields in the response header required by a specified response, for example, the Content-type response header. For details about common response headers, see Table 4.
    Table 4 Common response headers



    Mandatory or Not



    Standard HTTP header, which specifies the date and time at which the message was sent. The format is defined by RFC 822.


    Mon, 12 Nov 2007 15:55:01 GMT


    Standard HTTP header, which includes the software information that the server uses to process the request.




    Standard HTTP header, which specifies the size of the entity body, in decimal number of bytes, sent to the recipient.




    Standard HTTP header, which specifies the media type of the entity body sent to the recipient.



Response Body

A response body is generally returned in a structured format (for example, JSON or XML), corresponding to Content-type in the response header, and is used to transfer content other than the response header.

Sending a Request

You can send a request based on the constructed request body using any of the following three methods:

  • cURL

    cURL is a command-line tool used to perform URL operations and transfer information. cURL acts as an HTTP client that can send HTTP requests to the server and receive response messages. It is applicable to API debugging. For more information about cURL, visit https://curl.haxx.se/.

  • Code

    You can call APIs using code to assemble, send, and process request messages.

  • REST clients

    Both Mozilla Firefox and Google Chrome provide a graphical browser plug-in, that is, REST client, to send and process requests. For Mozilla Firefox, see Firefox REST Client. For Google Chrome, see Postman Interceptor.