From: Rick Jones <rick.jones2@hp.com>
To: Yuchung Cheng <ycheng@google.com>, Erik Grinaker <erik@bengler.no>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: TCP connection issues against Amazon S3
Date: Tue, 06 Jan 2015 11:16:27 -0800 [thread overview]
Message-ID: <54AC348B.4030900@hp.com> (raw)
In-Reply-To: <CAK6E8=d5Z0W5sSAdeEcecKbqjj_UwGw4949=a20fetFpLVKwwA@mail.gmail.com>
>>>>>> A packet dump [1] shows repeated ACK retransmits for some of the
> TCP does not retransmit ACK ... do you mean DUPACKs sent by the receiver?
>
> I am trying to understand the problem. Could you confirm that it's the
> HTTP responses sent from Amazon S3 got stalled, or HTTP requests sent
> from the receiver (your host)?
>
> btw I suspect some middleboxes are stripping SACKOK options from your
> SYNs (or Amazon SYN-ACKs) assuming Amazon supports SACK.
The TCP Timestamp option too it seems.
Speaking of middleboxes... It is probably a fish that is red, but a
while back I stepped in a middle box (a load balancer) which decided
that if it saw "too many" retransmissions in a given TCP window that
something was seriously wrong and it would toast the connection. I
thought though that was an active reset on the part of the middlebox.
(And the client was the active sender not the back-end server)
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.
rick jones
next prev parent reply other threads:[~2015-01-06 19:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5DCDADEF-FF9C-4844-8A2C-62E2D3B3B8CE@bengler.no>
2015-01-06 16:04 ` TCP connection issues against Amazon S3 Eric Dumazet
2015-01-06 16:11 ` Erik Grinaker
2015-01-06 17:20 ` Eric Dumazet
2015-01-06 18:17 ` Erik Grinaker
2015-01-06 18:32 ` Eric Dumazet
2015-01-06 18:33 ` Yuchung Cheng
2015-01-06 19:01 ` Erik Grinaker
2015-01-06 19:18 ` Yuchung Cheng
2015-01-06 19:42 ` Erik Grinaker
2015-01-06 20:13 ` Eric Dumazet
2015-01-06 20:26 ` Erik Grinaker
2015-01-06 21:04 ` Erik Grinaker
2015-01-06 22:00 ` Yuchung Cheng
2015-01-07 13:31 ` Erik Grinaker
2015-01-07 15:58 ` Eric Dumazet
2015-01-07 20:37 ` Erik Grinaker
2015-01-07 21:33 ` Eric Dumazet
2015-01-08 17:47 ` Erik Grinaker
2015-01-08 18:15 ` Eric Dumazet
2015-01-08 18:52 ` Rick Jones
2015-01-07 21:33 ` Yuchung Cheng
2015-01-07 1:23 ` Lukas Tribus
2015-01-07 13:06 ` Erik Grinaker
2015-01-06 19:16 ` Rick Jones [this message]
2015-01-06 19:48 ` Rick Jones
2015-01-06 19:50 ` Erik Grinaker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54AC348B.4030900@hp.com \
--to=rick.jones2@hp.com \
--cc=eric.dumazet@gmail.com \
--cc=erik@bengler.no \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).