You could configure the lucene data source to auto rotate logs more
frequently. If logs are large recovery takes longer time.
-Johan
On Mon, Oct 17, 2011 at 11:37 PM, Nuo Yan wrote:
> What if in production due to whatever reason the neo4j server died and in
> the case people have to start up a n
What if in production due to whatever reason the neo4j server died and in
the case people have to start up a new server with the current snapshot of
data (which would be data from a non-clean shut down). In such case, I don't
think it's acceptable to table lots of time (hours for large indices) to
It might be that you're not shutting down the server correctly (bin/neo4j
stop) or that it's shut down at the same time as there are transactions
running. Could you supply your data/graph.db/messages.log to me or look in
it to see if there are any lines containing:
Close invoked with
An examp
Dima,
are you shutting down your database correctly? Make sure you can
database.shutdown() and wait for it to finish ...
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter http://twi
Dear list members,
Each time I restart my server based on Neo4J I can see this in the logs:
Sep 1, 2011 7:23:17 PM
org.neo4j.kernel.impl.transaction.xaframework.XaLogicalLog
doInternalRecovery
INFO: Non clean shutdown detected on log [/opt/data/nioneo_logical.log.2].
Recovery started ...
Sep 1, 2
5 matches
Mail list logo
