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. It made the scheduler eat itself and would make the machine unresponsive. Sometimes the kernel would recognize it and try to kill it, other times you would have to reboot the machine.
On Feb 16, 1:40 pm, Kris Walker <[email protected]> wrote: > One of my EC2 machines (not part of a cluster) stopped responding to > my health checker the other day. I logged onto it and using `top` > discovered that the node.js process was hitting 99% cpu utilization > every time it received a request event. I killed the process and > restarted the server; when I started everything back up it was back > down to the normal 9-17% CPU utilization per request. You can see the > monitor data graph here:https://p.twimg.com/AlzFVjUCEAArq0C.pngIt's > been steadily ramping up for the past two weeks. > > * It is an micro EC2 instance > * The machine is running a low traffic Node.js webserver (~40 page > views per day) > * It is also running a very low traffic LAMP WordPress installation > (~2 page views per day) > > Normally I would say this is a memory leak, but the memory usage was > not reported to be very high by `top`. There is only one Node.js > process running on this machine, and it clearly hit 99% on every > request. Any idea why this would happen? -- 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
