I’m importing a load of polygons into a neo4j spatial index (neo4j 2.1.6 /
spatial 0.13-neo4j).
Each node is being added in it’s own individual transaction.
The system appears to be leaking files whilst doing this:
| Error Error running script run-script
src/groovy/load_mastermap_topographic_layer.groovy: java.lang.RuntimeException:
java.io.FileNotFoundException:
/Users/joe/Documents/Wansdyke/Git/network-database/db/src/truedb/data/truedb.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_2n9.prx
(Too many open files in system) (Use --stacktrace to see the full trace)
| Error Exception in thread "Lucene Merge Thread #3085"
| Error org.apache.lucene.index.MergePolicy$MergeException:
java.io.IOException: directory
'/Users/joe/Documents/Wansdyke/Git/network-database/db/src/truedb/data/truedb.db/schema/index/lucene/51'
exists and is a directory, but cannot be listed: list() returned null
| Error at
org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:509)
| Error at
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:482)
| Error Caused by: java.io.IOException: directory ‘
tmp/thedb.db/schema/index/lucene/51' exists and is a directory, but cannot be
listed: list() returned null
| Error at
org.apache.lucene.store.FSDirectory.listAll(FSDirectory.java:230)
| Error at
org.apache.lucene.store.FSDirectory.listAll(FSDirectory.java:241)
| Error at
org.apache.lucene.index.IndexFileDeleter.refresh(IndexFileDeleter.java:335)
| Error at
org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3922)
| Error at
org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:388)
| Error at
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:456)
And, yes, there appear to be a load of open files:
joe$ lsof -p 89310 | grep thedb.db | wc -l
6317
Loads of lucine index files...
thedb.db/schema/index/lucene/51/_4q3.cfs
thedb.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_2n5.cfs
thedb.db/schema/index/lucene/51/_4pp.cfs
thedb.db/schema/index/lucene/51/_4pw.cfs
thedb.db/schema/index/lucene/51/_4pq.cfs
thedb.db/schema/index/lucene/51/_4pr.cfs
thedb.db/schema/index/lucene/51/_4pd.cfs
thedb.db/schema/index/lucene/51/_4ph.cfs
thedb.db/schema/index/lucene/51/_4pv.cfs
thedb.db/schema/index/lucene/51/_4pf.cfs
thedb.db/schema/index/lucene/51/_4qb.cfs
thedb.db/schema/index/lucene/51/_4pg.cfs
thedb.db/schema/index/lucene/51/_4qo.cfs
thedb.db/schema/index/lucene/51/_4pt.cfs
thedb.db/schema/index/lucene/51/_4pj.cfs
thedb.db/schema/index/lucene/51/_4q5.cfs
thedb.db/schema/index/lucene/51/_4qk.cfs
thedb.db/schema/index/lucene/51/_4q0.cfs
thedb.db/schema/index/lucene/51/_4q8.cfs
thedb.db/schema/index/lucene/51/_4q6.cfs
thedb.db/schema/index/lucene/51/_4q7.cfs
thedb.db/schema/index/lucene/51/_4qa.cfs
thedb.db/schema/index/lucene/51/_4q9.cfs
thedb.db/schema/index/lucene/51/_4pu.cfs
thedb.db/schema/index/lucene/51/_4qg.cfs
thedb.db/schema/index/lucene/51/_4py.cfs
thedb.db/schema/index/lucene/51/_4ql.cfs
thedb.db/schema/index/lucene/51/_4px.cfs
thedb.db/schema/index/lucene/51/_4qs.cfs
thedb.db/schema/index/lucene/51/_4pz.cfs
thedb.db/schema/index/lucene/51/_4r2.cfs
thedb.db/schema/index/lucene/51/_4qe.cfs
thedb.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_2n2.cfs
thedb.db/schema/index/lucene/51/_4qn.cfs
thedb.db/schema/index/lucene/51/_4ra.cfs
thedb.db/schema/index/lucene/51/_4r3.cfs
[cut]
etc
Why would they be being leaked? Is this a known problem that been fixed in a
later spatial?
Thanks,
Joe
--
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.
