[ZBX-18914] Perfomance issue with Zabbix Agent2 and vfs.fs.get Created: 2021 Jan 25 Updated: 2025 Feb 27 Resolved: 2021 Jun 14 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent (G) |
Affects Version/s: | 5.0.7 |
Fix Version/s: | 5.0.13rc1, 5.4.2rc1, 6.0.0alpha1, 6.0 (plan) |
Type: | Problem report | Priority: | Major |
Reporter: | Igor Gorbach (Inactive) | Assignee: | Eriks Sneiders |
Resolution: | Fixed | Votes: | 1 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() |
||||||||||||||||
Issue Links: |
|
||||||||||||||||
Team: | |||||||||||||||||
Sprint: | Sprint 74 (Mar 2021), Sprint 75 (Apr 2021), Sprint 76 (May 2021), Sprint 77 (Jun 2021) | ||||||||||||||||
Story Points: | 1 |
Description |
Create some nfs share on remote host mount it on host with zabbix agent2 installed Make nfs share unavailable (for example - shut down the nfs-server machine) Run zabbix_get -s <host_ip> -p <zabbix_agent2_port> -k vfs.fs.get Result High load average on the host, all dependent items for vfs.fs.get key haven't working, timeout option hasn't working
|
Comments |
Comment by Eriks Sneiders [ 2021 Jun 10 ] |
Fixed in:
|