[ZBXNEXT-6898] Deprecate EOL database engines and upgrade requirements for the LTS 6.0 (min database version support) Created: 2021 Aug 16 Updated: 2024 Apr 10 Resolved: 2021 Oct 17 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Documentation (D), Frontend (F), Packages (C), Proxy (P), Server (S) |
Affects Version/s: | 6.0 (plan) |
Fix Version/s: | 6.0.0alpha3, 6.0 (plan) |
Type: | Change Request | Priority: | Critical |
Reporter: | Zabbix Support Team (EU) | Assignee: | Jurijs Klopovskis |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Oracle |
Issue Links: |
|
||||||||||||||||||||
Team: | |||||||||||||||||||||
Sprint: | Sprint 80 (Sep 2021) | ||||||||||||||||||||
Story Points: | 3 |
Description |
Hello Zabbix LTS releases are supported for Zabbix customers during five (5) years i.e. 3 years of Full Support (general, critical and security issues) and 2 additional years of Limited Support (critical and security issues only). In accordance with LTS policy database engines with EOL state should not be considered as a proper solution for release. The following database engines are considered EOL or near-EOL state or have blocker problems for Zabbix can be considered as NOT supported:
Support the following versions with an additional Server/Proxy configuration option (for example, AllowUnsupportedDbVersions) to allow versions which are not considered as stable/tested for LTS 6.0 release:
Recommended for LTS 6.0:
Additional reasons to the EOL of the products:
Official database engine repositories provide good quality packages ready for production use instead of an outdated ones. Main operating systems are covered from all engines with a suggested policy:
As a Zabbix user i would like to have exact recommendations, rather than - use any like MariaDB 5.5, but in two month you will face issues and need to spend 1 week, to move for another database |
Comments |
Comment by Jurijs Klopovskis [ 2021 Sep 17 ] |
Available in:
|
Comment by Jurijs Klopovskis [ 2021 Sep 20 ] |
Additional fix in:
|
Comment by Jurijs Klopovskis [ 2021 Oct 07 ] |
Bumped max postgresql version to 14.x 07e27fa5fea |
Comment by dimir [ 2022 Feb 22 ] |
Resulted in |