[ZBXNEXT-5040] Separate configuration and realtime fields in items table Created: 2019 Feb 14  Updated: 2019 Oct 24  Resolved: 2019 Sep 16

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: API (A), Frontend (F), Installation (I), Server (S)
Affects Version/s: None
Fix Version/s: 4.4.0alpha1, 4.4 (plan)

Type: Change Request Priority: Trivial
Reporter: Rostislav Palivoda Assignee: Viktors Tjarve
Resolution: Fixed Votes: 1
Labels: deadlock
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Causes
causes ZBX-16524 Aggregated checks not able to locate ... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
ZBXNEXT-5219 (Frontend) Separate configuration and... Change Request (Sub-task) Closed Roberts Lataria  
Team: Team A
Sprint: Sprint 56 (Sep 2019), Sprint 55 (Aug 2019), Sprint 49 (Feb 2019), Sprint 50 (Mar 2019), Sprint 51 (Apr 2019), Sprint 52 (May 2019), Sprint 53 (Jun 2019), Sprint 54 (Jul 2019)
Story Points: 3

 Description   

Items table used by server and frontend. Server frequently updates lastlogsize and locks the table. To reduce lock awaiting time we propose to split itemes table to keep realtime data in separate table. 



 Comments   
Comment by Oleksii Zagorskyi [ 2019 Feb 19 ]

Cross linking - deadlocks were discussed in ZBX-2494

Comment by Viktors Tjarve [ 2019 Jun 12 ]

Released in:

Comment by dimir [ 2019 Oct 24 ]

Keeping last value and clock in a separate table proposed in https://support.zabbix.com/browse/ZBX-13193?focusedCommentId=304714&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-304714

Generated at Fri Mar 29 17:13:46 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.