unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: "Tom Pesman" <tom@tnux.net>
To: "unicorn list" <mongrel-unicorn@rubyforge.org>
Subject: Re: Unicorn hangs on POST request
Date: Sun, 10 Mar 2013 17:22:35 +0100	[thread overview]
Message-ID: <ee3b6afe9db5d89951a2c79d4e66c9e1.squirrel@voorstraat46.tnux.net> (raw)
In-Reply-To: <20130309210227.GA29317@dcvr.yhbt.net>

> Tom Pesman <tom@tnux.net> wrote:
>> Hello,
>>
>> I'm trying to fix a problem I'm experiencing with my Rails
>> application hosted at Heroku. I've one POST request which hangs and
>> with the help of a customized rack-timeout gem
>> (https://github.com/tompesman/rack-timeout) I managed to get a
>> stacktrace: https://gist.github.com/tompesman/7b13e02d349aacc720e0
>>
>> How can I debug this further to get to the bottom of this and is
>> this a rack or a unicorn problem?
>
> It's a client or proxy problem.
>
> The request was too large to be transferred within your configured
> timeout, or the client or proxy layer was too slow at transferring the
> POST to unicorn, or the host running unicorn was too overloaded/slow
> to buffer the request.
>
> Factors:
> 1) Disk/filesystem/memory speed on the (client|proxy) talking to unicorn
> 2) Disk/filesystem/memory speed on the host running unicorn.
> 3) The network link between the (client|proxy) <-> unicorn.
>
> I don't know about Heroku, but nginx will fully buffer the request body
> before sending to unicorn, so all 3 factors are within your control.
>
> Does Heroku limit (or allow limiting of) the size of request bodies?
>
> Maybe a bad client sent a gigantic request.  nginx limits request bodies
> to 1M by default (client_max_body_size config directive).
>
> [1] unicorn buffers request bodies to TMPDIR via TeeInput
>

I agree with you if the POST request has a file to upload, but the
requests we're dealing with do not upload a file and are actually quite
small.

Example request (this is not a request that has failed, these are hard to
catch):
https://gist.github.com/tompesman/2e8ca417cdecb7580c9f

I've also made a dump of the env variable in the customized rack-timeout
middleware. This is a request that has failed.
https://gist.github.com/tompesman/1217d4f02aa33efcd873

Can I modify the my customized rack-timeout gem to get more information to
debug this problem?
https://github.com/tompesman/rack-timeout/blob/master/lib/rack/timeout.rb

Cheers,

-- 
Tom Pesman


_______________________________________________
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

  reply	other threads:[~2013-03-10 16:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09 16:02 Unicorn hangs on POST request Tom Pesman
2013-03-09 21:02 ` Eric Wong
2013-03-10 16:22   ` Tom Pesman [this message]
2013-03-11 19:49     ` Eric Wong
2013-03-11 22:20       ` Tom Pesman
2013-03-11 23:01         ` Eric Wong
2013-04-02 11:55           ` Tom Pesman
2013-04-02 17:24             ` Eric Wong
2013-04-02 20:25               ` Tom Pesman
2013-04-02 22:36                 ` Eric Wong
2013-04-03  4:56                   ` Lin Jen-Shin (godfat)
2013-04-03 11:38                     ` Eric Wong

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=ee3b6afe9db5d89951a2c79d4e66c9e1.squirrel@voorstraat46.tnux.net \
    --to=tom@tnux.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).