Hi Oliver, this could be covered by https://groups.google.com/forum/#!searchin/orient-database/Record$20Locking/orient-database/fD-UNnq9zmc/Gw1DiV6zK1EJ
Lvc@ On 21 October 2013 15:51, Oliver Saggau <[email protected]>wrote: > We want to migrate some parts of our relational database to OrientDB graph > database. We're using multiple loadbalanced servers for our REST based > application. Until now we have used database transactions and pessimistic > locking with "SELECT ... FOR UPDATE" to prevent concurrent modifications > from multiple threads (same server) or multiple request from different > servers. On the old googlecode wiki I have read that there are LockModes > for OGraphDatabase, but unfortunality the RECORD_LEVEL_LOCKING is not > allowed for "remote" connections. On the new github wiki the only thing > I've found is a approach using a for-loop with a retry count. But the > actual changes on the data for a specific request depend on a lot of things > and are actually calculated and applyed in many different methods. So it's > nearly impossible to just retry everything, because all changes made by the > calculations have to rolled back as well. No to metion the bad performance > when the calculations need be made all over again. > > One idea we've came up with is to create a special "locks" table inside > the relational database that were we insert one row per record. So > basically a table containing all records ids from OrientDB. That way would > could still use pessimistic locking with "SELECT rid FROM orientdb_records > WHERE rid = ... FOR UPDATE", but that's of course far from optiomal. Is > there really no way to achieve pessimistic locking (record-level) directly > in OrientDB for "remote" connections? > > -- > > --- > 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. > -- --- 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.
