From: "Lin Jen-Shin (godfat)" <godfat@godfat.org>
To: Eric Wong <e@80x24.org>
Cc: yahns-public@yhbt.net
Subject: Re: -1 shutdown_timeout?
Date: Wed, 23 Sep 2015 16:19:49 +0800 [thread overview]
Message-ID: <CAA2_N1vHUdyi-sWc7KnFEUWaENLJE1_wJtmsG7eZNwXUPVE3hg@mail.gmail.com> (raw)
In-Reply-To: <20150923080504.GA19141@dcvr.yhbt.net>
On Wed, Sep 23, 2015 at 4:05 PM, Eric Wong <e@80x24.org> wrote:
> "Lin Jen-Shin (godfat)" <godfat@godfat.org> wrote:
[...]
>> The timeout would be -1 after a few seconds, and then
>> it would only stop when those clients timeout at 60 seconds
>> (this is my assumption though, it would show a request was
>> around 60 seconds from CommonLogger (assumption again)
>> in the end, and yahns would quit gracefully)
>
> So your long request taking 60s is normal/expected? yahns
> *should* be waiting that long (unless you send another SIGQUIT).
>
> You can probably set a shutdown_timeout >= 60s to quiet down the log
> messages. It defaults to the highest client_timeout of all the apps
> running.
Looking at the code again (it's written long ago), yes you're right,
the polling would stop at 60s if there's no data available.
So I guess this is quite expected behaviour.
However instead of setting shutdown_timeout, I think I would probably
need to make the application know that the server is shutting down,
and stop right there instead of waiting for full 60 seconds.
Not sure if I could do this without talking to yahns directly...
>> I looked around the code, which should be:
>>
>> def dropping(fdmap)
>> if drop_acceptors[0] || fdmap.size > 0
>> timeout = @shutdown_expire < Yahns.now ? -1 : @shutdown_timeout
>> fdmap.desperate_expire(timeout)
>> true
>> else
>> false
>> end
>> end
>>
>> While Yahns.now would get growing, I don't really understand why
>> it's written like this? Is this intentional? If so, how could I force
>> yahns shut those clients down in this case?
>
> Rereading the code, it seems intentional and correct. Setting the -1
> timeout, means the shutdown_timeout has expired. yahns will not raise
> cross-thread exceptions or signals to interrupt apps, so I guess the use
> of the word "desperate" is a misnomer.
>
> Admittedly, the shutdown code is a bit hairy and it took me to a bit to
> fix some of the race conditions back in 2013.
Understood now. Thank you!
next prev parent reply other threads:[~2015-09-23 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 7:25 -1 shutdown_timeout? Lin Jen-Shin (godfat)
2015-09-23 8:05 ` Eric Wong
2015-09-23 8:19 ` Lin Jen-Shin (godfat) [this message]
2015-09-23 8:30 ` Eric Wong
2015-09-23 9:10 ` Lin Jen-Shin (godfat)
2015-09-23 9:31 ` Eric Wong
2015-09-23 9:49 ` Lin Jen-Shin (godfat)
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
List information: https://yhbt.net/yahns/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA2_N1vHUdyi-sWc7KnFEUWaENLJE1_wJtmsG7eZNwXUPVE3hg@mail.gmail.com \
--to=godfat@godfat.org \
--cc=e@80x24.org \
--cc=yahns-public@yhbt.net \
/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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/yahns.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).