Hey guys, Today we introduced OrientDB at scale to our production environment. It lives on a beefy machine with high memory and is correctly configured to make use of it.
Unfortunately, it fell over in the middle of the night and stopped responding. I had to kill the process and restart it -- after which things went back to normal. I should note that at the time, the load was pretty low, and CPU utilization was around 1% or so. I thought perhaps it was a fluke, but 12 hours later, sure enough it crashed again. This time, CPU usage seemed to spike to about 12%, and as did network output. Restarting it once more fixed the problem. Same thing again 15 minutes later -- lock up, had to restart it. I've tried perusing the logs to see if anything unusual pops up in there -- but I'm not finding anything. I'm using version 2.1.1 of OrientDB in standalone mode (not distributed). Are there any suggestions on why this might be happening and how I might be able to diagnose the root issue? Are there tools that I could use? I should note that I've stress tested OrientDB in the past with the queries that are in use. Any help would be appreciated! -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
