Database is unresponsive
Details
| Detail name | Value |
|---|---|
| Changelog Number | 19286 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 7.1.0 |
| Fix Versions | Exasol 7.1.27 |
| Resolution Date | 2024-05-21 |
Description
In rare cases, an internal process may cause the database to become unresponsive. In these scenarios, logins may be blocked, queries or transactions never complete, and statistics data is not logged in to the database. In these scenarios, the CPU load across all nodes falls to 0.
Workaround
The deadlock may be resolved by triggering the collection of backtraces. To trigger backtraces, you need to gather logs and select backtraces. To do this, see the below documentation: Backtrace Information.
If collecting backtraces does not resolve the deadlock, the database must be restarted.
Fix
The likelihood of encountering one of these scenarios is significantly reduced.
