Click MapReduce → Queries to view the list of MapReduce queries. The Queries page consists of a filter panel, a Sankey Diagram, and charts that display information about queries that you can group by Users or Queries. The Sankey diagram displays the flow of jobs from a selected queue to users and to the queries.
Note: The default time range is Last 24 hrs. To view statistics from a custom date range, click the icon and select a time frame and timezone of your choice.
The following metrics are displayed for each query group.
|Group Name||The name of the group filtered by User or Queries.|
|Query Count||The number of queries in the group.|
|Failed Queries||The number of queries that failed to execute.|
|Running Queries||The number of currently running queries.|
|Avg Memory||The average amount of memory consumed by a query group.|
|Total Memory||The total memory consumed by a query group.|
|Avg VCore||The average number of VCores used by a query group.|
|Total VCore||The total number of VCores used by a query group.|
|Avg Duration||The average time taken to execute queries in a query group.|
|Total Duration||The total time taken to execute queries in a query group.|
The following metrics are displayed for each query. Note: Click a query ID to view more details about the query in the Query Details page.
|ID||The ID of a query.|
|User||The user who executed the query.|
|Queue||The queue that the query belongs to.|
|Duration||The time taken to execute the query.|
|Status||The final state of the query run by the user. The state can be: Failed, Finished, Compiled.|
|Start Time||The time at which the query started.|
|Completion Time||The time at which the query completed execution.|
|Memory||The amount of memory consumed in executing the query.|
|VCores||The number of VCores used in query processing.|
|HiveServer2||The IP address of the installed host.|
Advanced Search Options
The search field in the MapReduce Queries page supports Influx-like query statements. For example, if you want to search for a query, use the format parametername:value. However, you need to know the full name of the parameter to be able to use it. For example, the name of the parameter visible in the UI is User. However, internally, the parameter name is effective_user. Hence, if you want to search for queries with User = Mark, you need to type effective_user:Mark.