DNS Shotgun merge requestshttps://gitlab.nic.cz/knot/shotgun/-/merge_requests2024-03-25T20:51:28+01:00https://gitlab.nic.cz/knot/shotgun/-/merge_requests/97Abort if the number of discarded packets exceeds limit2024-03-25T20:51:28+01:00Tom KrizekAbort if the number of discarded packets exceeds limitDiscarded packets indicate either invalid packets in the input, or a
runtime issue during replay. To avoid processing tainted data, abort the
traffic replay with an error if that happens.
The threshold of discarded packets is set at 0.1...Discarded packets indicate either invalid packets in the input, or a
runtime issue during replay. To avoid processing tainted data, abort the
traffic replay with an error if that happens.
The threshold of discarded packets is set at 0.1 % of the total packets.
Each traffic sender thread does its own accounting of this limit. The
threshold is only checked once 100 discarded packets are detected to
provide some leeway when the packet numbers are low.
Closes #44
---
Prereq !93https://gitlab.nic.cz/knot/shotgun/-/merge_requests/93Abort traffic replay if servers are unresponsive2024-03-21T10:47:18+01:00Tom KrizekAbort traffic replay if servers are unresponsiveIf the target server doesn't send any reply within the configured time
limit (when some are expected), abort the traffic replay. This most
commonly happens due to either incorrect configuration or server crash.
In the case of premature e...If the target server doesn't send any reply within the configured time
limit (when some are expected), abort the traffic replay. This most
commonly happens due to either incorrect configuration or server crash.
In the case of premature exit, ensure that existing statistics are
collected.
The default (baked-in) server timeout limit is configured to be 16
seconds. This has proven to be the right magic number in the development
of related tools (respdiff). It is unlikely that this limit would have
to be reconfigured or disabled, so no way to adjust or turn off this
limit is provided until a reasonable use-case is presented.
Closes #32