Possible database slow down and database restart due to high memory consumption of objectserver (II)
Details
| Detail name | Value |
|---|---|
| Changelog Number | 6446 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASOL 6.0.0 |
| Fix Versions | Exasol 6.1.0, Exasol 6.0.13 |
| Resolution Date | 2018-11-08 |
Problem Descriotion
The objectserver is part of Exasol server process architecture. It takes care of transactions, database objects and query cache. Internal testing has shown that memory consumption has increased with very frequent use of system tables. This has been fixed.
High memory consumption of the objectserver process can lead to a significant slow down of the database or even session terminations or a system restart when the database finally runs out of memory.
How to Identify
The TEMP_DB_RAM columns of the EXA_MONITOR system table family does include memory usage of the internal service processes. If this column shows a rising tendency that can not be explained by user-generated load, your system may be affected.
However, the memory consumption of distinct service processes can only be analyzed from logfiles. Please address our Support Team if you suspect that your system is affected by this issue.
Workaround
At this point the only known workaround is to restart the database.
