Avoid performance degradation in workloads with many transaction conflicts
Details
| Detail name | Value |
|---|---|
| Changelog Number | 24186 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.0.0 |
| Fix Versions | Exasol 8.34.0, Exasol 8.29.10 |
| Resolution Date | 2025-04-16 |
Description
The database prints detailed information about each transaction conflict to the log file, e.g. when a transaction is blocked by another transaction and has to wait for it's commit. In some high-load scenarios, this information may be printed too often, which can degrade database performance.
Workaround
Disable the output of transaction conflicts by setting the DB parameter "-visualizeTransactionConflicts=0" (see Add Database Parameters).
Fix
The problem has been fixed by reducing the number of retries to get the object lock, which reduces the number of conflicts that need to be printed.
