From: Laurens Pit <laurens.pit@mirror42.com>
To: Unicorn List <mongrel-unicorn@rubyforge.org>
Subject: Should USR2 always work?
Date: Tue, 22 Nov 2011 10:14:34 +1100 [thread overview]
Message-ID: <F2C54DC9-D848-4ECF-8A6E-6E20D95A58CD@mirror42.com> (raw)
Hi,
When deploying new code we go through the USR2 QUIT sequence. This works very nicely and gives zero downtime.
My question is whether there are instances when this sequence is known to not work, and instead you should really send QUIT first and then start all over?
I didn't expect that to be the case, but in the past year occasionally I've experienced I had to resort to QUIT and start all over in order to get all components loaded correctly.
Specifically: yesterday I upgraded several projects to rails 3.0.11 and added a new i18n .yml file in the config dir. After the USR2 QUIT sequence all new code seemed to work fine. Except the new .yml file wasn't loaded. Another run of USR2 and QUIT didn't resolve it. Only after QUIT and start of unicorn was the new .yml file loaded.
This was not just on one machine, which might have been a fluke. This was on all machines for all projects, consistently.
Any ideas?
Cheers,
Lawrence
_______________________________________________
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
next reply other threads:[~2011-11-22 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 23:14 Laurens Pit [this message]
2011-11-22 1:16 ` Should USR2 always work? Eric Wong
2011-11-22 1:55 ` Lawrence Pit
2011-11-22 3:00 ` Eric Wong
2011-11-23 5:31 ` Lawrence Pit
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=F2C54DC9-D848-4ECF-8A6E-6E20D95A58CD@mirror42.com \
--to=laurens.pit@mirror42.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).