OrientDB v1.6.1 Hi, While using a Java application to upload a large quantity of data to a new graph, I used the the console.sh to query the number of entities loaded as a way of determining the application's progress. This query caused the Java application to crash with an Exception indicating that it had timed out waiting for an exclusive write lock to the database. The application crashed almost immediately after the console query was submitted indicating that this timeout period is limited to a few seconds. Since we anticipate some long-running (i.e. hours) data loads in the future we are concerned about this type of database behavior.
1. Is this timeout period configurable, and if so how is it configured? 2. Is there a semaphore/lock that a Java application can test/acquire before attempting a database commit? 3. What orientdb database management practices can be followed to avoid this type of crash in the future? Thanks. Fred -- --- 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/groups/opt_out.
