Messages in this thread | | | Date | Tue, 06 Jan 2015 11:48:21 -0800 | From | Rick Jones <> | Subject | Re: TCP connection issues against Amazon S3 |
| |
On 01/06/2015 11:16 AM, Rick Jones wrote: > I'm assuming one incident starts at XX:41:24.748265 in the trace? That > does look like it is slowly slogging its way through a bunch of lost > traffic, which was I think part of the problem I was seeing with the > middlebox I stepped in, but I don't think I see the reset where I would > have expected it. Still, it looks like the sender has an increasing TCP > RTO as it is going through the slog (as it likely must since there are > no TCP timestamps?), to the point it gets larger than I'm guessing curl > was willing to wait, so the FIN at XX:41:53.269534 after a ten second or > so gap.
Should the receiver's autotuning be advertising an ever larger window the way it is while going through the slog of lost traffic?
rick
| |