[ZBX-7006] deleted/disabled item data never removed from trend cache Created: 2013 Sep 13 Updated: 2022 Dec 22 Resolved: 2016 Jan 15 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.8rc1, 3.0.0alpha3 |
| Type: | Incident report | Priority: | Blocker |
| Reporter: | richlv | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | cache, fragmentation, trends | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
if an item is disabled or deleted, it's data still stays in the trend cache. in a dynamic environment (with hosts/items being added/removed constantly) this can result in quite a lot of wasted space in the trend cache |
| Comments |
| Comment by Oleksii Zagorskyi [ 2015 Sep 30 ] |
|
Every 2-3 weeks zabbix server on a very dynamic environment just stops because there is no free space in trends cache. |
| Comment by Marc [ 2015 Oct 06 ] |
|
Does zabbix[wcache,trend,pfree] report effective free space? |
| Comment by Oleksii Zagorskyi [ 2015 Oct 06 ] |
|
According to a graph I have from a zabbix installation, the key value is decreasing constantly until it reaches 0%. |
| Comment by Glebs Ivanovskis (Inactive) [ 2015 Oct 13 ] |
|
Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-7006 revision 56108. |
| Comment by dimir [ 2015 Oct 14 ] |
|
Tested, please review r56151. glebs.ivanovskis Thanks, accepted! |
| Comment by Glebs Ivanovskis (Inactive) [ 2015 Oct 14 ] |
|
Fixed in pre-3.0.0alpha3 (trunk) r56160. Some implementation details. Every hour at 55 minutes (hardcoded) one of history syncer processes will iterate through the trend cache and remove trend cache entries for items which received no data in the current hour (if the first reading comes in last 5 minutes the entry will be recreated). The whole process should not take too long and will not affect other syncers unless they want a lock on trend cache. Usual trend cache operation has not been changed. |
| Comment by Glebs Ivanovskis (Inactive) [ 2015 Oct 15 ] |
|
Documented in What's new in Daemon improvements section: |
| Comment by dimir [ 2015 Oct 15 ] |
|
Added small changes, other than that - great! |
| Comment by OFN Team [ 2015 Oct 23 ] |
|
Guys are you going to backport this fix for 2.4? This is still a real issue which is forcing us to restart server one time 2-3 weeks. |
| Comment by Alexander Vladishev [ 2016 Jan 08 ] |
|
The issue must be ported into 2.4.x. Reopened. |
| Comment by Glebs Ivanovskis (Inactive) [ 2016 Jan 11 ] |
|
Backported to pre-2.4.8rc1 r57547. |
| Comment by Glebs Ivanovskis (Inactive) [ 2016 Jan 11 ] |
|
(1) Moved description from https://www.zabbix.com/documentation/3.0/manual/introduction/whatsnew300 to https://www.zabbix.com/documentation/2.4/manual/introduction/whatsnew248#daemon_improvements Please review. martins-v Reviewed, CLOSED |