unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: mongrel-unicorn@rubyforge.org
Cc: Pierre Baillet <oct@fotonauts.com>
Subject: Fwd: Support for Soft Timeout in Unicorn
Date: Thu, 3 Jun 2010 17:37:49 +0000	[thread overview]
Message-ID: <20100603173749.GA19649@dcvr.yhbt.net> (raw)


HTML attachments are wasteful and thus rejected from the mailing list.
On the other hand, it actually helps to include the patch itself
(inline) so it's readable without a (human) context switch :)

----- Forwarded message from Pierre Baillet <oct@fotonauts.com> -----

Subject: Fwd: Support for Soft Timeout in Unicorn
From: Pierre Baillet <oct@fotonauts.com>
To: unicorn@bogomips.org


Just tried to send that through the ml, but it seems something went wrong...


---------- Forwarded message ----------
From: <mongrel-unicorn-owner@rubyforge.org>
Date: Thu, Jun 3, 2010 at 2:40 PM
Subject: Support for Soft Timeout in Unicorn
To: oct@fotonauts.com

The message's content type was not explicitly allowed

---------- Forwarded message ----------
From: Pierre Baillet <oct@fotonauts.com>
To: mongrel-unicorn@rubyforge.org
Date: Thu, 3 Jun 2010 14:16:01 +0200
Subject: Support for Soft Timeout in Unicorn

We use Unicorn at fotopedia since yesterday in production. We switched from
Passenger due to an issue in the way Passenger was handling some error in
our main application. Things run very well on Unicorn.

We have also modified Unicorn to handle a soft timeout for its workers. The
Unicorn timeout was killing the workers without any chance for us to catch
the Rails stack trace and identify the issue. I've forked and branched
Unicorn from github and added a soft_timeout configuration value that is
used for long running workers.

The workers now handle SIGABRT and will raise an exception. This will crash
the Rails application if it can be crashed and force the framework to dump
the stack trace in the logs. Let me know if this might be useful for other
people and, why not, integrate that in the main Unicorn code !


Pierre Baillet <oct@fotonauts.com>

Pierre Baillet <oct@fotonauts.com>

----- End forwarded message -----
Unicorn mailing list - mongrel-unicorn@rubyforge.org
Do not quote signatures (like this one) or top post when replying

             reply	other threads:[~2010-06-03 17:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 17:37 Eric Wong [this message]
2010-06-03 18:06 ` Support for Soft Timeout in Unicorn Pierre Baillet
2010-06-03 18:22 ` Fwd: " Eric Wong
2010-06-03 18:32   ` Pierre Baillet
2010-06-03 18:47     ` Eric Wong
2010-06-03 19:38       ` Chris Wanstrath
2010-06-03 19:40         ` Pierre Baillet
2010-06-09 13:17           ` Pierre Baillet
2010-06-11  1:56             ` Eric Wong
2010-06-04 20:59         ` Eric Wong
2010-06-18 20:13           ` Ryan Tomayko
2010-06-18 21:48             ` Eric Wong
2010-06-21 19:03               ` Ryan Tomayko

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:

  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=20100603173749.GA19649@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=mongrel-unicorn@rubyforge.org \
    --cc=oct@fotonauts.com \


* 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


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).