-
Notifications
You must be signed in to change notification settings - Fork 871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Database import fails #2985
Comments
Have you already tried importing it without server but as embedded using plocal URL? |
Good idea! I tried this now. Result is the same :-( Strange, it seems that as bigger I make -Xmx, the less records I get into the database. With default JVM memory config default.pcl grew until 1.4 GB, with -Xmx2048m it failed earlier at about 766MB. Any idea is appreciated! *********console.sh output Importing records...
Error: com.orientechnologies.orient.core.db.tool.ODatabaseExportException: Error on importing database 'workplace' from file: /home/atsd/orientdb-export.json.gz Error: com.orientechnologies.orient.core.exception.OStorageException: Error on creating record in cluster: com.orientechnologies.orient.core.storage.impl.local.paginated.OPaginatedCluster@15189ac Error: com.orientechnologies.orient.core.exception.OStorageException Error: java.lang.OutOfMemoryError |
How much memory PHYSICAL do you have on your PC and free before to start importer? |
Free is 1300 MB, and there are few GB virtual memory available. |
Ok, java ... -Xmx512M -Dstorage.diskCache.bufferSize=600 ... |
This worked perfectly for me. Thank you very much! |
Dear OrientDB-Team,
I am fighting with a 4.1 GB large database export. I tried version 1.7.7 and now 1.7.9 with default configuration (except that I added -Xmx2048m to server.sh).
My export contains about 20,000 small PDF-Files. As I import it (using console.sh) into a fresh created database it crashes the database server JVM. What could I try?
With best wishes from Germany
Jörg
At the side of console.sh I get this exception:
At the server side I get:
orient-server.log is empty.
The text was updated successfully, but these errors were encountered: