v5.7.9
This bugfix release addresses an issue encountered while scaling down intake-head.
This release contains a bug fix to v5.7.8. Refer to the release notes for v5.7.4 and v5.7.8 to see other notable feature announcements and information concerning the v5.7 minor release.
prod scale profile users may need to scale turbine-api
By default in versions v5.7.x, the prod scale profile has the following settings:
- The
turbine-apipods have1Giof memory and1CPU. - The turbine_api_worker_count tunable is set to
8workers. This value may be overridden in the Hydrolix spec configuration.
For clusters using the prod scale profile, make the following adjustments to the scale of the turbine-api pod in the Hydrolix spec configuration based on the value of the turbine_api_worker_count tunable:
turbine-api scaling guidance:
- 8 workers: A minimum of
1.7Gimemory and1CPU - 16 workers: A minimum of
2.74Gimemory and2CPU - 32 workers: A minimum of
6.80Gimemory and3CPU
Upgrade⚓︎
Do not skip minor versions when upgrading or downgrading
Skipping versions when upgrading or downgrading Hydrolix can result in database schema inconsistencies and cluster instability. Always upgrade or downgrade sequentially through each minor version.
Example:
Upgrade from 5.5.0 → 5.6.x → 5.7.4, not 5.5.0 → 5.7.4.
Upgrade on GKE⚓︎
Upgrade on EKS⚓︎
Upgrade on LKE⚓︎
Changelog⚓︎
Bug Fixes⚓︎
Operator fixes⚓︎
- While scaling down
intake-head, the operator now waits untilintake-headterminates before terminating the correspondingturbine-server. This avoids data loss while scaling down ingest.