Native cloud deployment on Azure is not available for this version of Exasol, but you can install Exasol as a Linux application on Azure instances. For more information, see Installation.

Native cloud deployment on Google Cloud is not available for this version of Exasol, but you can install Exasol as a Linux application on Google Cloud instances. For more information, see Installation.

TEMP_DB_RAM_LIMIT is not checked system wide but per node

Details

Detail name	Value
Changelog Number	11998
Type	Bug
Status	Resolved
Affected Versions	Exasol 7.0.0
Fix Versions	Exasol 7.0.11
Resolution Date	2021-07-16

Background

Consumer Groups allow to limit the TEMP_DB_RAM usage in the system by defining different TEMP_DB_RAM_LIMIT options (see EXASOL-2639).
The TEMP usage of a query can be checked in system tables e.g. EXA_SQL_LAST_DAY and EXA_DBA_AUDIT_SQL.

Description

The limit set is wrongly applied per node-level instead of system-wide.
This results in queries only being terminated when their TEMP usage is roughly numberOfNodes*TEMP_DB_RAM_LIMIT.

Workaround

Reduce the TEMP_DB_RAM_LIMIT roughly by the number of nodes.

Fix

The limit is applied to the system usage of TEMP.

Changed behavior

TEMP_DB_RAM_LIMIT is now (correctly) applied to the system usage of TEMP instead of to the node usage of TEMP, resulting in earlier query aborts due to TEMP DB RAM usage.