Resource management properties#

All properties described in this page are defined as follows, depending on the deployment type:

  • Kubernetes: In the additionalProperties section of the the top-level coordinator and worker nodes in the values.yaml file.

  • Starburst Admin:: In the files/coordinator/config.properties.j2 and files/worker/config.properties.j2 files.

query.max-cpu-time#

  • Type: duration

  • Default value: 1_000_000_000d

This is the max amount of CPU time that a query can use across the entire cluster. Queries that exceed this limit are killed.

query.max-memory-per-node#

  • Type: data size

  • Default value: (JVM max memory * 0.3)

This is the max amount of user memory a query can use on a worker. User memory is allocated during execution for things that are directly attributable to, or controllable by, a user query. For example, memory used by the hash tables built during execution, memory used during sorting, etc. When the user memory allocation of a query on any worker hits this limit, it is killed.

Warning

The sum of query.max-memory-per-node and memory.heap-headroom-per-node must be less than the maximum heap size in the JVM on the node. See JVM config.

Note

Does not apply for queries with task level retries enabled (retry-policy=TASK)

query.max-memory#

This is the max amount of user memory a query can use across the entire cluster. User memory is allocated during execution for things that are directly attributable to, or controllable by, a user query. For example, memory used by the hash tables built during execution, memory used during sorting, etc. When the user memory allocation of a query across all workers hits this limit it is killed.

Warning

query.max-total-memory must be greater than query.max-memory.

Note

Does not apply for queries with task level retries enabled (retry-policy=TASK)

query.max-total-memory#

  • Type: data size

  • Default value: (query.max-memory * 2)

This is the max amount of memory a query can use across the entire cluster, including revocable memory. When the memory allocated by a query across all workers hits this limit it is killed. The value of query.max-total-memory must be greater than query.max-memory.

Warning

query.max-total-memory must be greater than query.max-memory.

Note

Does not apply for queries with task level retries enabled (retry-policy=TASK)

memory.heap-headroom-per-node#

  • Type: data size

  • Default value: (JVM max memory * 0.3)

This is the amount of memory set aside as headroom/buffer in the JVM heap for allocations that are not tracked by Trino.

Warning

The sum of query.max-memory-per-node and memory.heap-headroom-per-node must be less than the maximum heap size in the JVM on the node. See JVM config.

exchange.deduplication-buffer-size#

Size of the buffer used for spooled data during Fault-tolerant execution.