Disabling the cache monitor can result in many cleanup deadlocks and coredumps
Details
| Detail name | Value |
|---|---|
| Changelog Number | 7571 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 6.1.0 |
| Fix Versions | Exasol 6.1.3 |
| Resolution Date | 2019-03-12 |
Problem description
The cache monitor is an internal structure that retrieves recommendations for the ideal sizing of the database ram. It can be deactivated with the additional command line parameter "-cacheMonitorLimit = 0". This will disable the cache monitor at database startup. This deactivation was temporarily recommended for huge systems that suffered from performance issues. In Version 6.1, the deactivation of the cache monitor can result in a huge number of cleanup deadlocks in the SQL process, creating coredumps.
Workaround
Activate the cache monitor again. There should be no negative impact on performance. To do this, remove the command line parameter "-cacheMonitorLimit = 0".
