Inconsistent error messages when consumer group limits reached
Details
| Detail name | Value |
|---|---|
| Changelog Number | 14260 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 7.0.0, Exasol 7.1.0 |
| Fix Versions | Exasol 7.1.26, Exasol 8.26.0 |
| Resolution Date | 2024-03-15 |
Background
The resource manager with consumer-group specific configurations can be used to limit individual resource consumption.
When then such a limit is reached during query execution (e.g. SESSION_TEMP_DB_RAM_LIMIT) the current query (exceeding this limit) is aborted raising the corresponding exception e.g.
Successfully reconnected after system consumer group SESSION_TEMP_DB_RAM_LIMIT limit reached, transaction was rolled back.
Description
In some cases a controlled shutdown of the session is not possible in time, causing a broader exception:
Successfully reconnected after internal server error, transaction was rolled back.
Workaround
There is no workaround.
Fix
The correct exception referencing the consumer group is raised.
