I'm wondering if anyone is working on a graceful restart solution for paster?
While working with pylons in a production environment, I noticed that when we restarted after a deploy, we would see a spike in 500's. This was caused by multiple factors, but high up in the list was the fact that the default paster restart command kills the old process without letting active worker threads finish. I did just a little bit of hacking to try to see what I could come up with, and was wondering if I could get feedback on this, and who was the right person to coordinate with and submit patches too? (semi-related, I hear pyramid might be ditching paster, who's a good person to talk to about that?) Thanks! Fred -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
