[ZBXNEXT-2816] Timer process uses only one core (Use "No data collection" in maintenance periods) Created: 2015 May 18 Updated: 2020 Jul 30 Resolved: 2020 Jul 30 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Server (S) |
| Affects Version/s: | 2.4.5 |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Minor |
| Reporter: | Rodin Mikhail | Assignee: | Zabbix Development Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | maintenance, performance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Centos 6.5 (64 bit), Zabbix 2.4.5 |
||
| Issue Links: |
|
||||||||
| Description |
|
In large environment, where the hosts go out of maintenance periods zabbix.timer process is fully utilization one CPU core and blocking the work of the monitoring system. Maintenance periods: ~300 If you use maintenance periods with the option "With data collection" - the problem is not repeated. |
| Comments |
| Comment by Marc [ 2015 May 18 ] |
|
Similar to |
| Comment by Oleksii Zagorskyi [ 2015 May 19 ] |
|
(1) [D] It's mentioned also on https://www.zabbix.com/documentation/2.2/manual/appendix/config/zabbix_server:
The lost detail should be returned. |
| Comment by Rodin Mikhail [ 2015 May 19 ] |
|
It may be worth to redesign the timer process mechanism? |
| Comment by Alexander Vladishev [ 2020 Jul 30 ] |
|
Closed as duplicate of |