An infrastructure scaling operation will no longer wait for the database to be up
Details
| Detail name | Value |
|---|---|
| Changelog Number | 27329 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.0.0 |
| Fix Versions | Exasol 2025.1.5, Exasol 2025.2.0 |
| Resolution Date | 2025-12-05 |
Description
Calling job infra_db_scale would time-out on bigger databases. This was caused by the job waiting for the database and its workers to be running and connectable.
Workaround
This time-out can be ignored, as otherwise the scaling operation itself has already been successful.
Fix
The job no longer waits for the database to be running or connectable. It falls outside the responsibility of this job. There are other means (like using job db_info) to wait for a database.
Changed behavior
Confd job `infra_db_scale` no longer waits for the scaled database to be running. It still triggers a start if it was running when the job was called. Worker clusters will not be started under any circumstance.
