James Cox <[email protected]> wrote: > Hey, > > So here are some tasks for managing unicorn: > > https://gist.github.com/1121076
Can we ignore the :restart task? It's a bit fragile since it doesn't wait for the old process to die (SIGTERM means kill-as-quickly-as-possible, but given a loaded system it can still take some time). > I've found that it's very unreliable for quitting / terminating > unicorn and restarting with new code. When doing rapid deployments > particularly, i've found that i have to go in and kill -9 the master > process, and start again. If you SIGQUIT/SIGTERM before the app is loaded, the signal could be ignored. This behavior should probably change... > any thoughts on why it seems ineffective? > > Thanks. Which version of Unicorn are you using? I recall some minor tweaks to avoid/minimize race conditions over the years so maybe some are fixed. > PS: here's the unicorn config: > > https://gist.github.com/0dd07c5ad00c56d161c7 Avoid the top piece of the before_fork hook to TTOU workers, it's needlessly complex for most deployments unless you're really memory-constrained. -- Eric Wong _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
