Currently not able to access same JNL file from two JVMs.
If JNL file is already loaded by one JVM and I try to access same JNL from another JVM it throws an exception.
Is multiple JVM accessing same JNL is restricted from bigdata API or their is any mechanism to achieve it ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The HAJournalServer in the development branch provides high availability through quorum-based replication. This is a shared nothing architecture. Queries are answered against the local Journal. Updates are asynchronously replicated and the journals are synchronized at each 2-phase commit point.
It is not possible to have the same journal file opened for two different processes in the same JVM. The file is both read and written. The processes would not be able to coordinate these operations or on the same machine.
You can have multiple views open on the same AbstractTripleStore on the same Journal within the same JVM. This is how concurrent query is supported. Only one (unisolated) writer at a time, but multiple concurrent readers and the readers will be non-blocking.
Thanks,
Bryan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Currently not able to access same JNL file from two JVMs.
If JNL file is already loaded by one JVM and I try to access same JNL from another JVM it throws an exception.
Is multiple JVM accessing same JNL is restricted from bigdata API or their is any mechanism to achieve it ?
The HAJournalServer in the development branch provides high availability through quorum-based replication. This is a shared nothing architecture. Queries are answered against the local Journal. Updates are asynchronously replicated and the journals are synchronized at each 2-phase commit point.
It is not possible to have the same journal file opened for two different processes in the same JVM. The file is both read and written. The processes would not be able to coordinate these operations or on the same machine.
You can have multiple views open on the same AbstractTripleStore on the same Journal within the same JVM. This is how concurrent query is supported. Only one (unisolated) writer at a time, but multiple concurrent readers and the readers will be non-blocking.
Thanks,
Bryan