Btw, running OrientDB 2.1.9. On Friday, April 8, 2016 at 10:05:33 AM UTC+10, Erik Pragt wrote: > > Hi all, > > As the question title suggests, our OrientDB database crashed today. We > got notified by our monitoring server that our sites aren't accepting any > requests anymore, which was quickly traced to OrientDB being unavailable, > i.e., not running anymore. > > However, when checking the logs (orientdb.err/orientdb.log), there was no > indication at all of any crash. What can I do to investigate this issue, > and, even better, prevent OrientDB from crashing again? This isn't the > first time OrientDB crashes, but usually it's with an OutOfMemory > exception, which we fixed(?) by giving it more memory. Currently, the DB > hardly does anything (1 request per 10 seconds?), and we're a bit worried > that once we do get some requests, that OrientDB might crash more often. > > Our current settings to run OrientDB look like this: > > ORIENTDB_SETTINGS="-Dprofiler.enabled=true" > JAVA_OPTS_SCRIPT="-Djna.nosys=true -XX:+HeapDumpOnOutOfMemoryError > -Djava.awt.headless=true -Dfile.encoding=UTF8 -Drhino.opt.level=9" > > # ORIENTDB MAXIMUM HEAP. USE SYNTAX -Xmx<memory>, WHERE <memory> HAS THE > TOTAL MEMORY AND SIZE UNIT. EXAMPLE: -Xmx512m > MAXHEAP=-Xmx1024m > # ORIENTDB MAXIMUM DISKCACHE IN MB, EXAMPLE, ENTER > -Dstorage.diskCache.bufferSize=8192 FOR 8GB > #MAXDISKCACHE="" > MAXDISKCACHE="-Dstorage.diskCache.bufferSize=8192" > > If we need to provide some more information, please let me know. > > Kind regards, > > Erik Pragt >
-- --- 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
