From: Andrey Dmitrov <andrey.dmitrov@oktetlabs.ru>
To: Neal Cardwell <ncardwell@google.com>
Cc: Netdev <netdev@vger.kernel.org>,
"Alexandra N. Kossovsky" <Alexandra.Kossovsky@oktetlabs.ru>,
Konstantin Ushakov <kostik@oktetlabs.ru>
Subject: Re: TCP connection will hang in FIN_WAIT1 after closing if zero window is advertised
Date: Tue, 16 Sep 2014 13:29:16 +0400 [thread overview]
Message-ID: <541802EC.1060308@oktetlabs.ru> (raw)
In-Reply-To: <CADVnQym0NmF-Cqz=OEpVBmMAe6T-G1jmoq=fbVWtL7_Ny-wn3w@mail.gmail.com>
On 15/09/14 23:43, Neal Cardwell wrote:
> On Mon, Sep 15, 2014 at 12:11 PM, Andrey Dmitrov
> <andrey.dmitrov@oktetlabs.ru> wrote:
>> It is possible to create a lot of connections in the same manner which will be in FIN_WAIT1 state forever.
> ...
>> After ~10 minutes you will see 500 connections in the FIN_WAIT1 state on the host_A:
>> netstat | grep FIN_WAIT1 | wc -l
>> 500
> Thanks for the report. In your tests, have you ever seen the number of
> such connections exceed net.ipv4.tcp_max_orphans?
>
> Can you set net.ipv4.tcp_max_orphans to a low value and verify that it
> limits the number of such connections? AFAICT it should.
I tried to set net.ipv4.tcp_max_orphans to 100, it limits the
connections number. As I saw net.ipv4.tcp_max_orphans can be exceeded,
but for a short time. Maximum connections number in FIN_WAIT1 state was
196, after that it was decreased rather fast to ~100.
Thanks,
Andrey
next prev parent reply other threads:[~2014-09-16 9:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 16:11 TCP connection will hang in FIN_WAIT1 after closing if zero window is advertised Andrey Dmitrov
2014-09-15 19:43 ` Neal Cardwell
2014-09-16 9:29 ` Andrey Dmitrov [this message]
2014-09-15 23:15 ` Hannes Frederic Sowa
2014-09-15 23:37 ` Yuchung Cheng
2014-09-16 12:49 ` Andrey Dmitrov
2014-09-16 1:50 ` Eric Dumazet
2014-09-16 8:37 ` Hannes Frederic Sowa
2014-09-16 12:47 ` Andrey Dmitrov
2014-09-16 13:09 ` Eric Dumazet
2014-09-16 14:08 ` Andrey Dmitrov
2014-09-16 15:11 ` Yuchung Cheng
2014-09-16 16:31 ` Neal Cardwell
2014-09-16 17:04 ` Eric Dumazet
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=541802EC.1060308@oktetlabs.ru \
--to=andrey.dmitrov@oktetlabs.ru \
--cc=Alexandra.Kossovsky@oktetlabs.ru \
--cc=kostik@oktetlabs.ru \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
/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).