[ZBXNEXT-4444] Integrated Database Partitioning Created: 2018 Mar 23 Updated: 2018 Mar 26 Resolved: 2018 Mar 26 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | None |
| Affects Version/s: | 4.0 (plan) |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Major |
| Reporter: | Stoyan Stoyanov | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
I am not sure whether the database partitioning has been added in the new Zabbix 4.0 version but if it is not it would be very useful if there is an out of the box database partitioning in Zabbix. The Zabbix housekeeper process is ineffective for large environments. |
| Comments |
| Comment by Marc [ 2018 Mar 23 ] |
|
Imho does creation and maintaining of table partitioning not belong into applications. That's the job of the DBMS resp. DBA. |
| Comment by Stoyan Stoyanov [ 2018 Mar 23 ] |
|
The easier management is a plus for everyone. It could be optional or mandatory. For sure, it is a must-have for large environments and it would be better if there is a standard integrated and its compatibility is maintained during the Zabbix version updates. |
| Comment by Marc [ 2018 Mar 24 ] |
|
The point is, there is no standard way of table partitioning. Neither among different RDBMS engines, nor within a particular one. The way to implement it depends on individual needs and resources. Applying a standard setup would very likely lead to a poor implementation for most cases. The configuration of table partitioning is fairly simple - it's just the variables that have to be considered correctly. I'd argue, if this subject is considered to be difficult, then it's not for you. In larger environments its usually common practice and a "no brainer". |
| Comment by Glebs Ivanovskis (Inactive) [ 2018 Mar 26 ] |
|
Closing as Duplicate of ZBXNEXT-806. |