Hi, PLocal accesses database files, locking them at jvm level. It means that in a single JVM instance you can open the same plocal db as many times as you want. If you have different processes (deployed on different JVMs), they will be able to access the db in plocal only one at a time. You have some alternatives: 1) let a process start and embedded server in plocal and other processes access it in remote (see http://orientdb.com/docs/last/Embedded-Server.html) 2) run multiple nodes in plocal, in distributed mode, one per process
I hope it helps Luigi 2015-09-21 16:14 GMT+02:00 Bilal Nadeem <[email protected]>: > Hi, > > I'm currently creating a new application which will require a graph DB. > Essentially I will have a set of REST Services behind a load balance. > These rest services will be connecting to this DB. Will Persistent > embedded/Plocal work in this case? If multiple services are using the same > plocal address, will it cause conflicts? Also, I would l to run the > OrientDB under cluster mode with high availability. > > I'm planning to use OrientDB as graph and heavy use on graph traversal > (shortest path). > > Thanks > > > > > -- > > --- > 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. > -- --- 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.
