Database crash caused by high system heap setting
Details
| Detail name | Value |
|---|---|
| Changelog Number | 17327 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 7.0.0, Exasol 7.1.0, Exasol 8.0.0 |
| Fix Versions | Exasol 7.1.22, Exasol 8.20.0 |
| Resolution Date | 2023-07-12 |
Description
If the database has the maximum system heap memory (-maxSystemHeapMemory) set to a value larger than 64 GB and attempts to use more than 64 GB of system heap memory, the database will crash.
Workaround
Set the parameter to the current maximum limit of system heap (-maxSystemHeapMemory=65534)
Fix
The Exasol parameter '-maxSystemHeapMemory' is now checked at startup and only accepts values up to the maximum limit. If the database is started and this parameter has a value greater than the maximum limit, the limit is automatically reduced and a warning is generated in EXAoperation.
If the system reaches the maximum limit, the sessions with the most heap memory usage will be aborted with a proper error message.
Please note that the max system heap memory was increased from 64 GB to 128 GB in Changelog 17490.
Changed behavior
The Exasol parameter '-maxSystemHeapMemory' is now checked at startup to ensure that it is not above the maximum limit . If it is above the maximum limit, the limit will automatically be reset to the maximum limit and an EXAoperation warning will be generated. Exasol will then continue to start normally.
