Impala Daemon Thrift Server Connections Test
Thrift server is a protocol for the applications developed in different programming languages for communication purpose and it is the one which receives the request or queries from client programs. The Impala Daemon Thrift Server Connections test tracks the thrift server connections to Impala Daemon and reports on their status and usage.
Target of the test : Apache Impala
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for the target Impala Daemon server.
Parameter | Description |
---|---|
Test period |
How often should the test be executed. |
Host |
The IP address of the target server that is being monitored. |
Port |
The port number through which the Apache Impala communicates. The default port is 25000. |
Impalad URL |
Each daemon server has a different endpoint URL. You need to configure the eG agent with the endpoint URL of each daemon, so that the agent can access the URL and pull metrics on the health of the target daemon servers. Specify such URL in the Impalad URL text box . To know how to configure the eG agent with the API Endpoint URLs, refer to Configuring the eG agent with the API Endpoint URLs topic in Pre-requisites for Monitoring Apache Impala. |
Impalad Authorization type |
To access daemon server, you need to configure Digest authorization. Digest authorization is a method used to verify the identity of a user requesting access to API Endpoint URL of the daemon server. Digest authorization uses a combination of a username, password, and a unique message digest (a type of encrypted code). Specify such Digest authorization value in the Impalad Authorization type text box considering the below criteria:
If multiple Impalad URLs are mentioned in the Impalad URL text box, then specify a comma-separated list of authorization type for each URL. For example, if there are two Impalad URLs, one URL without authorization and the other URL protected with authorization (username/password authorization), then specify Impalad Authorization type as: no_auth,digest_auth in the Impalad Authorization type text box. By default, Impalad Authorization type value is no_auth. |
Impalad User, Impalad Password and Confirm Password |
Once you enable web server access to the eG agent, make sure that 'password authentication' is also enabled. This is needed, so that the eG agent is able to access the built-in web server for each daemon in a safe, secure manner. Configure the credentials of such a user against Impalad User and Password text boxes. Confirm the password by retyping it in the Confirm Password text box. To know how to configure the eG agent with 'secure' access to the built-in web server, refer to Configuring the eG agent with 'secure' access to the built-in web server topic in Pre-requisites for Monitoring Apache Impala. By default, Impalad user parameter is set to none.
|
Statestored URL |
Each daemon server has a different endpoint URL. You need to configure the eG agent with the endpoint URL of each daemon, so that the agent can access the URL and pull metrics on the health of the target daemon servers. Specify such URL in the Statestored URL text box . To know how to configure the eG agent with the API Endpoint URLs, refer to Configuring the eG agent with the API Endpoint URLs topic in Pre-requisites for Monitoring Apache Impala. |
Statestored Authorization type |
To access daemon server, you need to configure Digest authorization. Digest authorization is a method used to verify the identity of a user requesting access to API Endpoint URL of the daemon server. Digest authorization uses a combination of a username, password, and a unique message digest (a type of encrypted code). Specify such Digest authorization value in the Statestored Authorization type text box considering the below criteria:
By default, Statestored Authorization type value is no_auth. |
Statestored User, Statestored Password and Confirm Password |
Once you enable web server access to the eG agent, make sure that 'password authentication' is also enabled. This is needed, so that the eG agent is able to access the built-in web server for each daemon in a safe, secure manner. Configure the credentials of such a user against Statestored User and Password text boxes. Confirm the password by retyping it in the Confirm Password text box. To know how to configure the eG agent with 'secure' access to the built-in web server, refer to Configuring the eG agent with 'secure' access to the built-in web server topic in Pre-requisites for Monitoring Apache Impala. By default, Impalad user parameter is set to none.
|
Catalogd URL |
Each daemon server has a different endpoint URL. You need to configure the eG agent with the endpoint URL of each daemon, so that the agent can access the URL and pull metrics on the health of the target daemon servers. Specify such URL in the Catalogd URL text box . To know how to configure the eG agent with the API Endpoint URLs, refer to Configuring the eG agent with the API Endpoint URLs topic in Pre-requisites for Monitoring Apache Impala. |
Catalogd Authorization type |
To access daemon server, you need to configure Digest authorization. Digest authorization is a method used to verify the identity of a user requesting access to API Endpoint URL of the daemon server. Digest authorization uses a combination of a username, password, and a unique message digest (a type of encrypted code). Specify such Digest authorization value in the Catalogd Authorization type text box considering the below criteria:
By default, Statestored Authorization type value is no_auth. |
Catalogd User, Catalogd Password and Confirm Password |
Once you enable web server access to the eG agent, make sure that 'password authentication' is also enabled. This is needed, so that the eG agent is able to access the built-in web server for each daemon in a safe, secure manner. Configure the credentials of such a user against Catalogd User and Password text boxes. Confirm the password by retyping it in the Confirm Password text box. To know how to configure the eG agent with 'secure' access to the built-in web server, refer to Configuring the eG agent with 'secure' access to the built-in web server topic in Pre-requisites for Monitoring Apache Impala. By default, Impalad user parameter is set to none.
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Backend connections |
Indicates the total number of Impala backend client connections made to this Impala Daemon. |
Number |
|
Backend connection rate |
Indicates the rate at which the Impala backend client connections are made to this Impala Daemon. |
Connections/mins |
|
Backend connection in use |
Indicates the number of active Impala backend client connections in this Impala Daemon. |
Number |
A high availability of this measure is required for the better performance of the target server. |
Backend connection setup queue size |
Indicates the number of Impala backend client connections in the Impala Daemon server that have been accepted but awaiting connection setup. |
Number |
|
Beeswax frontend connections |
Indicates the total number of Beeswax API connections made to this Impala daemon. |
Number |
|
Beeswax frontend connection rate |
Indicates the rate at which the Beeswax API connections are made to this Impala daemon. |
Connections/mins |
|
Beeswax frontend connection in use |
Indicates the number of active Beeswax API connections in this Impala daemon. |
Number |
A high availability of this measure is required for the better performance of the target server. |
Hiveserver2 frontend connections |
Indicates the number of Hiveserver2 API connections made to this Impala daemon. |
Number |
|
Hiveserver2 frontend connection rate |
Indicates the rate at which the Hiveserver2 API connections are made to this Impala daemon. |
Connections/mins |
|
Hiveserver2 frontend connection in use |
Indicates the number of active Hiveserver2 API connections in this Impala daemon. |
Number |
A high availability of this measure is required for the better performance of the target server. |