I noticed recently that Neo4j appears to dump a directory listing of the graph.db directory to the messages.log file on startup. For example it starts with entries like:
2014-11-17 18:53:56.597+0000 INFO [o.n.k.i.DiagnosticsManager]: index: 2014-11-17 18:53:56.597+0000 INFO [o.n.k.i.DiagnosticsManager]: lucene: 2014-11-17 18:53:56.597+0000 INFO [o.n.k.i.DiagnosticsManager]: node: 2014-11-17 18:53:56.597+0000 INFO [o.n.k.i.DiagnosticsManager]: node_auto_index: 2014-11-17 18:53:56.598+0000 INFO [o.n.k.i.DiagnosticsManager]: _104v.cfs: 2014-10-22T16:49:24-0400 - 672.32 kB I found this out while trying to figure out why our Neo4j servers sometimes take a while to start up even when they're not integrity-checking the Lucene index. We have implemented a Node version store that uses the file system to store previous versions of the state of Nodes in the graph.db. We figured there's no better place to root this version store than in the graph.db directory itself since we consider the versions to be part of the database. As you might imagine, this directory can get large. On my dev machine, I have over 30,000 files in my version store. According to messages.log, it took around 1.5 minutes just to write the directory listing to the log. Now, we can obviously put the version store somewhere else (e.g. the data directory), but before I do that I was wondering if someone could tell me what the purpose of that directory listing is and whether there's any way to disable it. Thanks! -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
