Alex Sharp <[email protected]> wrote: > > 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. > > We've noticed some of this behavior as well. We've seen the new master > start spinning and consume 100% cpu (according to top). The old master > and workers are still running and working, but the new master just > hangs, and we have to kill -9.
Can you try to strace (or equivalent) the old master to see what's using 100% CPU? -- 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
