From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: [PATCH] rework master-to-worker signaling to use a pipe
Date: Tue, 10 Dec 2013 01:58:24 +0000 [thread overview]
Message-ID: <20131210015824.GA20757@dcvr.yhbt.net> (raw)
In-Reply-To: <CAAtdryP-SJ4xyp-zStU06W0kVvhZdYHGHk9wvR_divcsdURreA@mail.gmail.com>
Sam Saffron <sam.saffron@gmail.com> wrote:
> Bottom line is that your change is not really required.
OK. However, the other benefit of the change is that master process
death can be detected much sooner. (The per-process open file limit
issue doesn't really bother me with my change, since the overall kernel
pipe usage does not change).
I suppose ruby-pg users can do something like:
trap(:EXIT) { pg.cancel }
if they really want to be able to abort in-progress queries
> Thanks you so much for being super responsive here. Sorry if I caused
> you to go on a tangent you did need to go on.
No worries, I was already using a similar method to (only) detect master
process death in another master-worker server. Anyways, there's nothing
pg-specific to it and I was always slightly worried signals would cause
some buggy code behave incorrectly in the face of EINTR (though most of
C Ruby + extensions seem well-behaved in that regard).
So I'm likely to go forward with it (if not for unicorn 4.8, then 5.0)
Thanks for bringing this issue to everyone's attention.
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
prev parent reply other threads:[~2013-12-10 1:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 9:52 [PATCH] rework master-to-worker signaling to use a pipe Eric Wong
2013-12-10 0:22 ` Sam Saffron
2013-12-10 1:58 ` Eric Wong [this message]
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/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131210015824.GA20757@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=mongrel-unicorn@rubyforge.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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.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).