Re: [Neo4j] Neo 4j backup and locking

48 views
Skip to first unread message

Lasse Westh-Nielsen

unread,
Mar 1, 2013, 4:55:16 AM3/1/13
to ne...@googlegroups.com
On Thu, Feb 28, 2013 at 9:24 PM, Clark Phillips <clark.r....@gmail.com> wrote:
Although a full backup allows for continued operations on the target instance --- it required? Can I configure neo4j to NOT apply any updates that occurred AFTER the backup command had been issued?

Clark,

One thing springs to mind: stop the instance, copy the store (the graph.db directory) and start it again as slave-only (http://docs.neo4j.org/chunked/stable/ha-how.html).

But I am wondering what your use case is?
 

Although a full backup does not require any locking ... is it possible to invoke a database-wide lock? If so, how?

I don't believe so. You could do it from your application, require all queries to lock a particular node?

 - Lasse

 

Clark Phillips

unread,
Mar 1, 2013, 10:09:22 AM3/1/13
to ne...@googlegroups.com, la...@neotechnology.com
On Friday, March 1, 2013 3:55:16 AM UTC-6, Lasse Westh-Nielsen wrote:
On Thu, Feb 28, 2013 at 9:24 PM, Clark Phillips <clark.r....@gmail.com> wrote:
Although a full backup allows for continued operations on the target instance --- it required? Can I configure neo4j to NOT apply any updates that occurred AFTER the backup command had been issued?

Clark,

One thing springs to mind: stop the instance, copy the store (the graph.db directory) and start it again as slave-only (http://docs.neo4j.org/chunked/stable/ha-how.html).

Lasse,

Do you have to stop the instance before copying the graph.db directory? Is there a problem with simply copying the graph.db directory while the instance is still running?
 


But I am wondering what your use case is?
I am trying to make a hot backup of both a mysql database and a neo4j database that are tightly coupled. It tricky because updates to one may ultimately result in updates to the other ... it is easy to make backups that are out of sync and I am trying to guarantee they are in sync.
 

 

Although a full backup does not require any locking ... is it possible to invoke a database-wide lock? If so, how?

I don't believe so. You could do it from your application, require all queries to lock a particular node?

Do you mean to lock each and every node on a node basis? Basically, iterate over every node and lock it?
Reply all
Reply to author
Forward
0 new messages