Fixed
Details
Assignee
Benjamin ReedBenjamin ReedReporter
Jesse WhiteJesse WhiteComponents
Sprint
NoneFix versions
Affects versions
Priority
Major
Details
Details
Assignee
Benjamin Reed
Benjamin ReedReporter
Jesse White
Jesse WhiteComponents
Sprint
None
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created February 28, 2017 at 1:24 PM
Updated April 6, 2017 at 2:56 PM
Resolved April 6, 2017 at 10:56 AM
With the changes introduced in NMS-8671, it is now possible to configure the retry behavior for various SNMP error status codes.
However, the trackers do not currently limit the number of retry attempts, and if the agent continues to respond with the same error, the client will continue to retry. This can cause bursts of CPU usage and network traffic and prevent certain functions such as a data collection from operating properly.
When performing retries, we should introduce some mechanism to limit the number of retry attempts made.