clusterLoad

URI

<serverStatus uri>/clusterload[.<format>]

Supported methods

GET, HEAD

Parent resource

serverStatus

Child resources

clusterMemberLoad

Introduction

clusterLoad is the cluster load monitoring resource, which can be used to monitor the cluster state, including the running status of each sub node and concurrent request access status. By monitoring sub nodes, you can view the current concurrent access status of each sub node, also can view the average access status. The server monitoring contents include specified service component and instance access status.

Supported Methods:

GET: gets the concurrent request information of the cluster system, including the running status and concurrent access amount of each sub node.
HEAD: Checks whether clusterLoad resource exists, or whether it can be accessed.

Supported output formats: RJSON、JSON、HTML、XML.

Resource hierarchy

HTTP request methods

Implement the HTTP request on the following URI, where supermapiserver is the server name, with rjson being the output format.

http://supermapiserver:8090/iserver/manager/serverstatus/clusterload.rjson

GET request

gets the concurrent request information of the cluster system, including the running status and concurrent access amount of each sub node.

Request parameter

Implement a GET request for clusterLoad resource, related parameters can be contained in URL:

Name	Type	Description
componentName	String	Service component name, which can be used alone.
interfaceName	String	Service interface name, which can't be used alone, must be used with componentName.

Response structure

Implement a GET request for clusterLoad resource, return the detailed concurrent request information of the whole cluster system, the representation structure of single sub node is as follows:

Field	Type	Description
averageTime	int	average response time of the server, and the unit is second.
currentCount	int	current concurrent amount of the server.
historicalAccessCounts	int[]	Records the concurrent amount within 5 minutes before the current time.
interval	int	Service access statistical time interval, the default is 1 second.
ip	String	the server IP.
memberId	String	the child node ID.
port	int	the port number of the server.

Response example

Implement a GET request for clusterLoad resource http://localhost:8090/iserver/manager/serverstatus/clusterload.rjson, the returned response result in rjson format is as follows:

[ { "averageTime": 0, "currentCount": 0, "historicalAccessCounts": null, "interval": 1, "ip": "192.168.17.182", "memberId": "f4a5f3f05619478caad7c8b51000827d", "port": 8090 }, { "averageTime": 0, "currentCount": 0, "historicalAccessCounts": [ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 5, 1, 3, 5, 7, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 4, 3, 2, 2, 3, 1, 1, 0, 0, 1, 0 ], "interval": 1, "ip": "192.168.17.16", "memberId": "7db62a86361e48b3aba3a8797468efe3", "port": 8091 }, { "averageTime": 0, "currentCount": 0, "historicalAccessCounts": [ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 7, 2, 4, 6, 6, 6, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 3, 4, 1, 4, 2, 1, 1, 3, 1, 0, 1, 4 ], "interval": 1, "ip": "192.168.17.16", "memberId": "20b012afb12640ab968df28a67cfd69e", "port": 8090 } ]

HEAD request

Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content. The meta-information includes the media-type, content-encoding, transfer-encoding, content-length, etc.

HEAD request can be used to check if the clusterLoad resource exists, or if the clusterLoad resource can be accessed by clients. It can also determine if the clusterLoad resource supports an output format <format> if performed on a URI with .<format> included.