unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Tom Burns <tom.burns@jadedpixel.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Combating nginx 499 HTTP responses during flash traffic scenario
Date: Thu, 29 Nov 2012 15:57:48 -0500	[thread overview]
Message-ID: <CAK4qKG0A6zNHwRGW9wEmpm+iBXnnJkan3i9AxgCKBkcvwQu=+w@mail.gmail.com> (raw)
In-Reply-To: <E7534814-055D-4216-A2FA-DD05009BBC25@gmail.com>

On Thu, Nov 29, 2012 at 3:41 PM, Eric Wong <normalperson@yhbt.net> wrote:
> I fixed up some minor line-wrapping, signed-off, and added your
> quote above to the commit message.  Pushed as
> commit 5c700fc2cf398848ddcf71a2aa3f0f2a6563e87b
> to git://bogomips.org/unicorn.git
>
> I'll tag and push a 4.5.0.preview1 gem soon

Excellent news :)

On Thu, Nov 29, 2012 at 3:30 PM, Lawrence Pit <lawrence.pit@gmail.com> wrote:
> we haven't tested it with older browsers
> such as IE6 (we do not have that requirement) nor with all of the API
> clients we see (java, python, etc., we do have that requirement).

With nginx and proxy_pass you can buffer the entire request/response
from the rails application, so clients will not notice any difference.

>
> Hopefully we're bringing that patch into our production environment within
> the next couple of weeks, and then we should see results later that week.
>
>
> Tom Burns wrote:
>>
>> Unexpectedly the patch also helped us ward off a DoS attack where the
>> attackers were disconnecting immediately after making a request.
>
>
> Awesome!
>
> The only thing that worries me is that Eric calls this a "nasty/crazy
> solution". :p Not sure why. Seems to me it's a rather smart solution that
> perhaps in the future would deserve to be the default.
>
> A related question: is it possible to get insight in what's in the unicorn
> queue and for how long requests have been queued there?

We use New Relic for response queue monitoring.

https://newrelic.com/docs/features/tracking-front-end-time

Cheers,
Tom
_______________________________________________
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:[~2012-11-29 20:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 17:44 Combating nginx 499 HTTP responses during flash traffic scenario Tom Burns
2012-10-29 18:45 ` Eric Wong
2012-10-29 19:27   ` Hongli Lai
2012-10-29 19:41     ` Eric Wong
2012-10-29 21:06       ` Hongli Lai
2012-10-29 21:53   ` Eric Wong
2012-10-29 22:21     ` Tom Burns
2012-10-30 20:40     ` Tom Burns
2012-10-30 21:37       ` Eric Wong
2012-11-02 17:59         ` Tom Burns
2012-11-02 19:38           ` Eric Wong
2012-11-03 22:45             ` Tom Burns
2012-11-05 11:48               ` Eric Wong
2012-11-06  3:16                 ` Tom Burns
2012-11-06 21:23                   ` Eric Wong
2012-11-29 15:52                     ` Tom Burns
2012-11-29 20:30                       ` Lawrence Pit
2012-11-29 20:57                         ` Tom Burns [this message]
2012-11-29 21:30                         ` Eric Wong
2012-11-30 23:47                           ` Eric Wong
2012-11-29 20:41                       ` Eric Wong
2012-12-04  3:00                         ` Eric Wong
2012-11-29 21:19                       ` Eric Wong
2012-11-29 21:55                         ` [RFC/PATCH] check_client_connection: document local-only requirement Eric Wong
2012-11-29 23:47                           ` Tom Burns

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='CAK4qKG0A6zNHwRGW9wEmpm+iBXnnJkan3i9AxgCKBkcvwQu=+w@mail.gmail.com' \
    --to=tom.burns@jadedpixel.com \
    --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).