Actions
Bug #3949
closedTransaction list grows without bound on parsers that use unidirectional transactions (5.0.x)
Description
The SNMP transaction vector length can grow to large values eventually causing packet loss due to excessive time spent in rs_snmp_get_tx_iterator.
At a production site, this manifested as
1. Packet loss: packet loss occurred at rates well within the machine's capacity. Packet loss was nearly always present.
2. Excessive time in rs_snmp_get_tx_iterator (as measured by perf). Several readings showed it with 45% of time spent (displayed by perf).
Through observations obtained by capturing live network traffic, the attached pcap was synthetically constructed to demonstrate the issue. The key thing is the unbalanced ratio of requests to responses.
Files
Updated by Jeff Lucovsky over 4 years ago
- Copied from Bug #3877: Transaction list grows without bound on parsers that use unidirectional transactions added
Updated by Jeff Lucovsky about 4 years ago
- Status changed from Assigned to In Review
- Assignee changed from Jeff Lucovsky to Jason Ish
Updated by Jason Ish about 4 years ago
- Subject changed from SNMP: Transaction vector grows without bound to SNMP: Transaction vector grows without bound (5.0.x)
Updated by Jason Ish about 4 years ago
- Subject changed from SNMP: Transaction vector grows without bound (5.0.x) to Unidirectional transaction handling (5.0.x)
Updated by Jason Ish about 4 years ago
- Subject changed from Unidirectional transaction handling (5.0.x) to Transaction list grows without bound on parsers that use unidirectional transactions (5.0.x)
Updated by Victor Julien about 4 years ago
- Status changed from In Review to Closed
Updated by Victor Julien about 4 years ago
- Affected Versions 5.0.0, 5.0.1, 5.0.2 added
Actions