Re: [Neo] Question regarding nioneo_logical.log

2010-03-18 Thread Mattias Persson
lf 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

Re: [Neo] Question regarding nioneo_logical.log

2010-03-18 Thread Rick Bullotta
: 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

Re: [Neo] Question regarding nioneo_logical.log

2010-03-18 Thread Tobias Ivarsson
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: Ne

Re: [Neo] Question regarding nioneo_logical.log

2010-03-18 Thread Rick Bullotta
al 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 r

Re: [Neo] Question regarding nioneo_logical.log

2010-03-18 Thread Tobias Ivarsson
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 tha

[Neo] Question regarding nioneo_logical.log

2010-03-17 Thread Rick Bullotta
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