Cool. So the only transactions that could be "lost" would be ones that were uncommitted prior to the crash.
-----Original Message----- From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On Behalf Of Tobias Ivarsson Sent: Thursday, March 18, 2010 9:55 AM To: Neo user discussions Subject: Re: [Neo] Question regarding nioneo_logical.log If the system crashes Neo4j will begin the next startup with a recovery phase. During the recovery phase the logical log will be replayed. This reapplies all committed transactions, bringing Neo4j back to the state it was in before the crash. Cheers, Tobias On Thu, Mar 18, 2010 at 2:27 PM, Rick Bullotta < rick.bullo...@burningskysoftware.com> wrote: > Thanks for the info. > > That triggers more questions, of course. > > So what happens if the system crashes before the log is rotated? Will all > of the transactions in the log be rolled back (even if they have already > been committed)? Or will they be "flushed" on startup? > > -----Original Message----- > From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] > On > Behalf Of Tobias Ivarsson > Sent: Thursday, March 18, 2010 5:34 AM > To: Neo user discussions > Subject: Re: [Neo] Question regarding nioneo_logical.log > > The logical log is rotated when it grows to 10M. When the log is rotated > the > data is "flushed" to the respective stores. > > What sizes are you seeing on the logical log? If its (much) larger than > 10M, > and you haven't configured Neo4j to use a larger logical log, then we will > need to look into why that is happening. > > Cheers, > Tobias > > On Wed, Mar 17, 2010 at 10:52 PM, Rick Bullotta < > rick.bullo...@burningskysoftware.com> wrote: > > > I notice this file growing rather large during system operation, even > > though > > we are doing very small transactions. It seems that the transaction are > > only "flushed" to the respective node, property, and relationship stores > on > > shutdown. This of course creates concern, since we are implementing an > > "always on" application that never shuts down (OK, in "theory"). AFAIK, > we > > are calling tx.finish() on each transaction. > > > > > > > > Thanks for any insights on whether this behavior is to be expected and/or > > possible causes if it isn't normal... > > > > > > > > Thanks! > > > > > > > > Rick > > > > > > > > _______________________________________________ > > Neo mailing list > > User@lists.neo4j.org > > https://lists.neo4j.org/mailman/listinfo/user > > > > > > -- > Tobias Ivarsson <tobias.ivars...@neotechnology.com> > Hacker, Neo Technology > www.neotechnology.com > Cellphone: +46 706 534857 > _______________________________________________ > Neo mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > > _______________________________________________ > Neo mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > -- Tobias Ivarsson <tobias.ivars...@neotechnology.com> Hacker, Neo Technology www.neotechnology.com Cellphone: +46 706 534857 _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
