For AI agents: the complete documentation index is at llms.txt. Every page is also available as markdown by appending .md to its URL, or by sending an Accept: text/markdown request header.

Resource groups

note

Resource groups are Enterprise only.

Resource groups isolate competing query workloads inside one instance. These settings are instance-wide. The per-group policy that decides admission, CPU share and memory budgets is set in SQL, not here. See Configure and use resource groups for those statements.

None of these settings are reloadable: changing any of them requires a restart.

Resource groups also require access control to be enabled (acl.enabled=true) before principals can be mapped to a group, and every pool that executes SQL must run in Fiber mode, which is the default. The requirements list the Fiber setting that governs each pool. What happens when a pool is in legacy mode depends on how the feature was turned on. Left at its default, it turns itself off and logs an error naming the pool and the setting to change. Asked for explicitly, it fails startup with the same error, because an explicit request and a legacy pool cannot both be honoured.

General​

resource.groups.enabled​

  • Default: true
  • Reloadable: no

Master switch. When false, resource group admission, CPU scheduling and group memory accounting are disabled. Group definitions and principal mappings remain in the catalog, so turning the feature back on restores the policies that were already there.

true also makes the catalog a hard dependency: an instance whose catalog cannot be read does not start, and a replica whose catalog is not current is not promoted. With false, both conditions are logged and ignored. See Behaviour under failure and on replicas.

Existing principal-specific and instance-default single-query memory limits continue to apply when resource groups are disabled.

Left unset, this resolves to false on an instance whose SQL pools are in legacy mode, so upgrading such an instance does not turn the feature on and does not stop the instance from starting. SHOW PARAMETERS then reports false, which is the value that took effect. Set it to true explicitly and a legacy pool becomes a startup error instead.

resource.groups.process.memory.limit.bytes​

  • Default: 0
  • Reloadable: no

Ceiling for tracked native query memory across all groups. 0 leaves the instance without a process ceiling, which is the default. When set, it bounds every group and every query, so no group policy can grant more than this.

An unlimited process budget does not disable memory accounting or remove an existing single-query limit. The group-level SQL parameter memory_limit treats 0 and UNLIMITED as no ceiling, as does RESET (memory_limit).

This is not a process RSS limit. It covers tracked query memory only, not JVM heap, memory-mapped table pages or long-lived engine caches.

See also​