Failure to scale db cluster up/down via ConfD job "infra_db_scale" leaves inconsistent state
Details
| Detail name | Value |
|---|---|
| Changelog Number | 22106 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.0.0 |
| Fix Versions | Exasol 8.33.0, Exasol 8.29.6 |
| Resolution Date | 2025-01-14 |
Description
When a ConfD job infra_db_scale to change the instance type of a DB cluster fails, e.g. due to missing capacity for the requested instance type from the cloud provider, the system would be left in an inconsistent state, where e.g. DBRAM was adjusted to the new instance types, but the new instances didn’t actually start.
Workaround
Please contact Exasol Support to recover the DB after a failed infra_db_scale attempt.
Fix
Such a failure should now always lead to a rollback of any configuration changes that were done to adjust to the new instance type and roll back to the old instance type if the requested one is not available.
