Thanks All: On Feb 17, 1:14 am, Christopher Jeffrey <[email protected]> wrote: > This might be an ec2 problem. Are you sure it was 100% cpu and not > just a 1.00+ system load? ec2 had a problem where node would get > thrown into the uninterruptible sleep state forever, waiting on io.
Yeah, I remember that thread about EC2 instances going into "sleep state" with Node.js. I don't think that is the issue, because I have a 3rd party health checker pinging it every 60 seconds. I'm not sure how to detect if the processor is running at 99%-100% or 1.00+ system load by AWS terms. `top` reported the Node.js process to hit 99% CPU every time it was hit with a request event. It reported 10% - 20% for the exact same requests after restarting. AWS says a micro instance will be throttled back if it persists above 1.00 CPU unit. Judging by the behavior of the instance, I think that is what happened. I'm trying to figure out how to prevent a process from crawling upwards over a period of time until the limit is being constantly hit. Right now the only solution is to kill it and start over. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" 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/nodejs?hl=en?hl=en
