Closed lholden closed 13 years ago
hmm can you quantify "forever"? because node's http sockets timeout after 2 minutes and i believe cluster also has a timeout option, so after that amount of time the child is killed regardless of open connections, which I think I have defaulting to two minutes as well
I mean until "node's http sockets timeout after 2 minutes" :D
ah! fewf haha. feel free to tweak that setting if you need to
reopened? still an issue or can I close?
Sorry, go ahead :)
On Jul 29, 2011 11:03 AM, "visionmedia" < reply@reply.github.com> wrote:
reopened? still an issue or can I close?
Reply to this email directly or view it on GitHub: https://github.com/LearnBoost/cluster/issues/133#issuecomment-1682867
I am having a problem were a worker will report that it has a connection active for quite a while after receiving its first connection. This does not seem to prevent the worker from handling additional requests... but it does make shutdown/restart/reload take forever.
Simple application to test this with (that replicates the issue for me anyhow)
server.coffee
app.coffee
stats() from the repl