[ZBXNEXT-5239] The ability to set the lifetime of the value cache values, when deleting items Created: 2019 May 27  Updated: 2024 Apr 10  Resolved: 2020 Jan 16

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: None
Fix Version/s: 4.0.17rc1, 4.4.5rc1, 5.0.0alpha1, 5.0 (plan)

Type: Change Request Priority: Trivial
Reporter: Edgar Akhmetshin Assignee: Vladislavs Sokurenko
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Causes
Team: Team A
Sprint: Sprint 56 (Sep 2019), Sprint 55 (Aug 2019), Sprint 53 (Jun 2019), Sprint 54 (Jul 2019), Sprint 57 (Oct 2019), Sprint 58 (Nov 2019), Sprint 59 (Dec 2019), Sprint 60 (Jan 2020)
Story Points: 1

 Description   

With the active use of LLD and API for adding and deleting items in dynamic environments using calculated items and the time shift function of triggers, the value cache is cleared rather slowly ([value cache|https://www.zabbix.com/documentation/4.0/manual/config/triggers/expression?s[]=value&s[]=cache#value_caching], ZBXNEXT-322), this leads to increased memory consumption.



 Comments   
Comment by AdminSup [ 2019 May 27 ]

Hello,

 

May i know we have any update on it?

 

Regards,

Huy Quoc NGUYEN

Comment by Vladislavs Sokurenko [ 2019 Jun 21 ]

It looks like currently if failed to allocate required memory then will remove items from value cache that were not accessed in last 24 hours, this is controlled by ZBX_VC_ITEM_EXPIRE_PERIOD.
This means that memory will fill up and get free again when out of memory. Is it something that you are experiencing ?

One of solutions would be to cleanup with some frequency, could it be enough in your case ?
The other solution is to make ZBX_VC_ITEM_EXPIRE_PERIOD configurable and cleanup with some frequency.

Comment by Vladislavs Sokurenko [ 2020 Jan 15 ]

Fixed in:

  • pre-4.0.17rc1 4a4be061f6a
  • pre-4.4.5rc1 a569a98db63
  • pre-5.0.0alpha1 (master) 9fd1f3010a8
Generated at Sat Apr 27 08:03:31 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.