[ZBX-8538] allow single retry on libnetsnmp level - it will give positive effect Created: 2014 Jul 28  Updated: 2022 Oct 08  Resolved: 2014 Oct 28

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 2.2.5, 2.3.2
Fix Version/s: 2.2.8rc1, 2.4.2rc1, 2.5.0

Type: Incident report Priority: Blocker
Reporter: Oleksii Zagorskyi Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: logging, retry, snmp, timeout
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by ZBX-9081 SNMP errors when bulk requests enabled Closed
is duplicated by ZBX-8964 SNMP agent item failed: first network... Closed

 Description   

When we introduced timeout for snmp in ZBX-4393 we also limited library's retries to 0.
There was a discussion and I'm still sure it was reasonable to limit library's retries (default was =5) as with server's timeout (which is often =30 in production) it would lead to big delays.

But after ZBXNEXT-98 in 2.2.3 and discovered and investigated ZBX-8528 (see more details in this issue namely) I suggest and ask to allow single retry on library level until we will not introduce ZBXNEXT-1096.

In any case it will have more positive effect than negative.
I spent enough time to weigh it

Even decreased rate of "first network error/recovering" because of random lost UDP packets in zabbix log is an improvement.

 Comments   
Comment by Aleksandrs Saveljevs [ 2014 Oct 23 ]

Fix in development branch svn://svn.zabbix.com/branches/dev/ZBX-8538 addresses this issue and provides a simple solution to ZBX-8528 (see a comment in that issue for more details).

Comment by Aleksandrs Saveljevs [ 2014 Oct 27 ]

Fixed in pre-2.2.8 r50193, pre-2.4.2 r50194, and pre-2.5.0 (trunk) r50195.

Comment by Aleksandrs Saveljevs [ 2014 Oct 27 ]

(1) Documented at:

wiper CLOSED

Generated at Thu Apr 25 04:11:17 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.