Can someone explain in more detail why the recovery takes so long and if there's a way to short-cut it? I am experiencing this too recently and it even happens after a clean shutdown. Right now, it's approx 30 min and unfortunately an unacceptable downtime in my company ;(
Thanks in advance, -Andreas Neil Ellis wrote: > Hi Johan > > That would be great, those are the things that will cause us problems > when we get to production. > > All the best > Neil > On 26 Jul 2009, at 13:07, Johan Svensson wrote: > > >> Hi Neil, >> >> It is possible to make Neo4j act as a read-only database resulting in >> no recovery after a non clean shutdown. We are planing to have a look >> at this after the b9 release. Also speeding up the recovery process is >> something we have to do before going 1.0 final (should be possible to >> drop the rebuild of id generator which is taking all the time during >> recovery). >> >> Regards, >> -Johan >> >> On Sun, Jul 26, 2009 at 2:35 AM, Neil Ellis<[email protected]> >> wrote: >> >>> Hi Guys >>> >>> So thanks for the plug for peepwl :-) I saw the slides from OSCON :-) >>> >>> Okay so we have a strong use case where we want to access Neo but >>> don't want to trigger a complete transaction recovery if Neo fails. >>> We're using Neo as read-only at this point. Recovery currently takes >>> about half an hour or an hour which is a lot of downtime. >>> >>> Is it possible to make it so that Neo doesn't do this check and acts >>> as a read-only database? >>> >>> All the best >>> Neil >>> >> _______________________________________________ >> Neo mailing list >> [email protected] >> https://lists.neo4j.org/mailman/listinfo/user >> > > _______________________________________________ > Neo mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
