Can you somehow reproduce this? Michael
> Am 28.03.2015 um 17:12 schrieb Josef Karthauser <[email protected]>: > > It doesn't appear to need lots of files for a read-only load, only when > writing. The number of open files appears to be proportional to the number of > nodes being saved, not the number of nodes in the database, and it retains > the open files indefinitely. Makes me think it's a leaking file handle > instead of a normal operational mode. > > Joe > > On Friday, March 27, 2015 at 11:19:16 PM UTC, Michael Hunger wrote: > Lucene needs many open files to work, > > what's your ulimit? recommended is 40.000 > > Michael > >> Am 27.03.2015 um 20:46 schrieb Dr Josef Karthauser <joe.kar...@ >> <>wansdyketele. <http://wansdyketele.com/>com <http://wansdyketele.com/>>: >> >>> On 27 Mar 2015, at 19:39, Dr Josef Karthauser <joe.kar...@ <>wansdyketele. >>> <http://wansdyketele.com/>com <http://wansdyketele.com/>> wrote: >>> >>> 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: >>> >>> [cut] >> >>> Why would they be being leaked? Is this a known problem that been fixed in >>> a later spatial? >> >> Trying a simple test with just 13 spatially indexes nodes (polygons) I end >> up with the following files still open at the end of the process: >> >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3ji.fdt >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3ji.fdx >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3ji.frq >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3ji.nrm >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3ji.prx >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3ji.tis >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3ji.tis >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3jj.cfs >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3jk.cfs >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3jl.cfs >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3jm.cfs >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3jn.cfs >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3jo.cfs >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3jp.cfs >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3jq.cfs >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3jr.fdt >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/_3jr.fdx >> test.db/index/lucene/node/topography__neo4j-spatial__LayerNodeIndex__internal__spatialNodeLookup__/write.lock >> test.db/schema/index/lucene/39/_6da.cfs >> test.db/schema/index/lucene/39/_6db.cfs >> test.db/schema/index/lucene/39/_6dc.cfs >> test.db/schema/index/lucene/39/_6dd.cfs >> test.db/schema/index/lucene/39/_6de.cfs >> test.db/schema/index/lucene/39/_6df.cfs >> test.db/schema/index/lucene/39/_6dg.cfs >> test.db/schema/index/lucene/39/_6di.cfs >> test.db/schema/index/lucene/39/_6dj.cfs >> test.db/schema/index/lucene/39/_6dk.cfs >> test.db/schema/index/lucene/39/_6dl.cfs >> test.db/schema/index/lucene/39/_6dm.cfs >> test.db/schema/index/lucene/39/_6dn.cfs >> test.db/schema/index/lucene/39/_6dp.cfs >> test.db/schema/index/lucene/39/_6dq.cfs >> test.db/schema/index/lucene/39/_6dr.cfs >> test.db/schema/index/lucene/39/_6ds.cfs >> test.db/schema/index/lucene/39/_6dt.cfs >> test.db/schema/index/lucene/39/_6du.cfs >> test.db/schema/index/lucene/39/_6dw.cfs >> test.db/schema/index/lucene/39/_6dx.cfs >> test.db/schema/index/lucene/39/_6dy.cfs >> test.db/schema/index/lucene/39/_6dz.cfs >> test.db/schema/label/lucene/_6dq.cfs >> test.db/schema/label/lucene/_6dr.cfs >> test.db/schema/label/lucene/_6ds.cfs >> >> That doesn’t look right. >> >> 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 neo4j+un...@ <>googlegroups.com <http://googlegroups.com/>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > 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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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.
