eG Monitoring
 

Measures reported by HiveServer2QueryTest

The real test of the performance of a data warehouse lies in how quickly the database responds to queries. Whenever users complaint of slow execution of their queries, administrators need to know the reason for the delay - is it because the queries themselves are badly designed? or is it because of some queries consuming too much of physical reads per execution? The Hive Queries test helps with this root-cause analysis.

This test monitors each database instance in the target Apache Hive data warehouse and reports the maximum number open and closed queries that exists as a result of query execution.

Outputs of the test: One set of results for the target Apache Hive

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
openQuery Indicates the number of open queries after query execution. Number

 
runCount Indicates the number of open queries after query execution. Number

Ideally, the value of this measure should be zero.
closedQuery Indicates the number of closed queries after query execution. Number