The THREAD_RESERVATION_AGGREGATE_LIMIT query option limits the number of
reserved threads for a query across all nodes on which it is executing. The option is
intended to prevent execution of complex queries that can consume excessive CPU or
operating system resources on a cluster. Queries that have more threads than this
threshold are rejected by Impala’s admission controller before they start executing.
For example, an Impala administrator could set a default value of
THREAD_RESERVATION_AGGREGATE_LIMIT=2000 for a resource pool on a 100 node
where they expect only relatively simple queries with less than 20 threads per node to
run. This will reject queries that require more than 2000 reserved threads across all
nodes, for example a query with 21 fragments running on all 100 nodes of the cluster.
You can override the default value per-query or per-session, in the same way as other
query options, if you do not want the default
THREAD_RESERVATION_AGGREGATE_LIMIT value to apply to a specific query or
session.
Syntax: SET THREAD_RESERVATION_AGGREGATE_LIMIT=number;
Type: numeric
Default: 0 (no limit)
Added in: Impala 3.1