Database Crash when an S3 request was retried too soon
Details
| Detail name | Value |
|---|---|
| Changelog Number | 22814 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.0.0, Exasol 8.29.3 |
| Fix Versions | Exasol 8.33.0, Exasol 8.29.6 |
| Resolution Date | 2025-01-14 |
Description
When DB storage performs a request to S3, it might fail and the storage service needs to retry. When the retry is happening too fast, the S3 service might not have recovered in time, which may lead to a database crash. There needs to be a backoff strategy for all failure types, to allow the service to recover eventually.
Workaround
No Workaround available.
Fix
The likelihood of encountering one of these scenarios is significantly reduced. This failure scenario cannot be avoided entirely since S3 might have a genuine outage which will still lead to a database outage.
