On Sat, Mar 8, 2008 at 12:45 AM, Aaron Crow <[EMAIL PROTECTED]> wrote: > Hi John, > > So as far as server app code dealing with a forced shutdown, may I ask what > you recommend for situations where there's some task running that really > should be allowed to complete? For example, would you have the concept of an > internal registry, where tasks are registered, and a shutdown signal means > "no new tasks allowed, and wait for running tasks to finish"? >
you're server should start returning something other than 200 from its happy page, and the HTTP-aware front end load balancer (which polls these pages) will stop routing traffic to it. That makes it implicit that new work doesn't come in. It also stops this box receiving work when it is unhappy for other reasons, like it can't talk to the database or there's no temp file storage.
