Sessions may be unable to execute commands for a while
Details
| Detail name | Value |
|---|---|
| Changelog Number | 10069 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 6.1.0, Exasol 6.2.0 |
| Fix Versions | Exasol 7.0.0, Exasol 6.2.7, Exasol 6.1.10 |
| Resolution Date | 2020-08-19 |
Problem
A session that is sending a damaged packet to the database may cause other sessions that are connected to the same database node to not be able to execute queries for some time.
For these sessions the EXA_*_SESSIONS system tables will still show IDLE in the STATUS column after a command has been sent.
Delays in query execution for sessions connected to this node can occur until the session with the damaged packet closed the connection or the database is restarted.
Logins on the affected node or query execution of sessions connected to other nodes are not impacted.
Fix
The handling of damaged packages is changed to make sure that there are no more delays.
Workaround
The database can be restarted
