[ZBXNEXT-782] Pollers should not be connected to the database Created: 2011 May 12  Updated: 2024 Apr 10  Resolved: 2020 Dec 08

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: None
Fix Version/s: 5.4.0alpha1, 5.4 (plan)

Type: Change Request Priority: Major
Reporter: Alexander Vladishev Assignee: Vladislavs Sokurenko
Resolution: Fixed Votes: 1
Labels: performance, scalability
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
 Summary
 Type
 Status
 Assignee
ZBXNEXT-1335 Pingers should not be connected to a ... Change Request (Sub-task) Closed  
Team: Team A
Sprint: Sprint 70 (Nov 2020), Sprint 71 (Dec 2020)
Story Points: 3

 Description   

Currently pollers have own connection to the database for updating statuses of items and hosts.

 Comments   
Comment by Alexander Vladishev [ 2011 May 24 ]

Added support of not-supported items by the history cache.
The development branch: svn://svn.zabbix.com/branches/dev/ZBXNEXT-782

Comment by Alexander Vladishev [ 2011 May 27 ]

Added support of processing not supported items by a history syncer in a version pre1.8.6, r19897.

Reopened this issue for implementing activation/deactivation hosts by a history syncer.

Comment by richlv [ 2011 Nov 24 ]

host activation/deactivation split out as ZBXNEXT-1040

Comment by Oleksii Zagorskyi [ 2012 Jan 29 ]

Just for record: for 2.0 branch implemented in version 1.9.5

Comment by Alexander Vladishev [ 2012 Jul 27 ]

The issue is completed partially. I reopen it.

Comment by Vladislavs Sokurenko [ 2020 Nov 30 ]

Implemented in:

  • pre-5.4.0alpha1 (master) 7c2a5143dc5

Updated documentation:

Comment by Constantin Oshmyan [ 2020 Nov 30 ]

Fix Version/s: 5.4.x

and

Implemented in:

  • pre-5.4.0alpha1 (master) faafb2c347c

Will this enhancement be implemented in other versions, for example 5.0.x (the current LTS)?

Comment by Vladislavs Sokurenko [ 2020 Nov 30 ]

Unfortunately it was not planned for any other versions due to major changes such as introduction of new process. Are you having issues due to many database connections, can you please describe the problem ?

Comment by Constantin Oshmyan [ 2020 Nov 30 ]

vso, we had problem only once (link to a ticket in Russian).
There was not enough connections to Zabbix database (PostgreSQL), because the default settings "max_connections = 100" in the postgresql.conf was too small. Tech. support engineers explained us that almost each Zabbix-server process has a connection to the database, not the history syncers only. The main trouble was this fact is not covered in documentation.

Comment by Vladislavs Sokurenko [ 2020 Nov 30 ]

I see, thank you for explanation, documenting which process use database connection would be nice addition.

Generated at Fri Apr 26 22:24:25 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.