On 21/10/2019 12:19, Mikael Pesonen wrote:
While testing RDF Delta, I'm following the instructions and have server
running:
java -jar delta-server.jar --mem
[2019-10-21 13:20:00] Delta INFO Provider: mem
[2019-10-21 13:20:00] Config INFO Delta Server port=1066
[2019-10-21 13:20:00] Delta INFO RDF Delta 0.8.0
2019-10-12T08:58:34+0000
[2019-10-21 13:20:00] Delta INFO No data sources
Connecting to it succeeded once
./dcmd ls --server http://localhost:1066/
-- No logs --
But never since. Restarting server doesn't help and the connection just
hangs, no timeout or any error.
Any idea what could cause that?
Works for me.
Are you sure the server processed isn't suspended? It does not run in
the background unless you put it in the background. Just suspending it
would behave much as you describe.
Andy
Mikael
On 19/10/2019 14:33, Andy Seaborne wrote:
RDF Delta [1] does this for a dataset (as "dataset" is the unit of
transactions, it is all related changes).
But if it is one graph out of a dataset, then it is more complicated -
any update may change both local and replicated graphs together. You
could have a special dataset that picks one the one graph to
replicated as a layer over the storage dataset and use Delta for that.
The other approach is if the updates to the replicated graph are
separate from the other graphs in which case, simply sending the
changes to each server may be a workable approach for you.
Andy
[1] https://afs.github.io/rdf-delta
On 18/10/2019 12:55, Mikael Pesonen wrote:
We have 3 servers each running an instance of Jena/Fuseki, one server
being the master. All servers have one graph in common, but they
contain other graphs too which contain server specific stuff and are
not to be synced.
Is there a tool that helps to sync the graph on other servers from
master automatically?
Br,
Mikael
