Make the 2-second timeout parameter configurable

Bug #634301 reported by Baron Schwartz
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Currently there is a hard-coded 2-second timeout that discards a session if activity is not seen for 2 seconds. This makes it impossible to measure queries longer than 2 seconds. Convert this into a command-line option and make the default 3600 seconds instead.

The worst-case wrong behavior is that an inbound packet is seen, the outbound response is not seen, another inbound packet appears but is not seen, and then we see the outbound response and associate it with the first inbound packet. This is unlikely, relative to the number of cases where at least one of the intermediate packets is seen.

The risk is that we accumulate stale sessions for up to an hour. However, these only use a small amount of memory, and should not be a problem. By making this parameter configurable, we can experiment with that.

Changed in tcprstat:
milestone: none → 0.9.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers