Memory leak on solr 3.6.2 indexing on NFS -


i have memory leak in solr 3.6.2 based app holds index on nfs. i've read it's not best practice hold solr index on nfs, got system heritage , can't change @ moment.

once in every x (configurable) minutes, system "wakes up" , starts index data collected during sleeping time. reads files , solr indexes it. problem memory of solr app gets larger , larger every indexing cycle. crashes oom, after several indexing cycles.

gclog graph

i took heapdump several times , tried analyze using eclipse memory analyzer. "remainder" section large

and seems consists of many org.apache.lucene.index.freqproxtermswriterperfield.freqproxpostingsarray unreachable objects: dominator_tree

is source of leak or normal?

another strange behavior more , more .nfs00000000000..... hidden files being generated in index directory (which located on nfs, noted before) every indexing cycle.

these files take lot of disk space, , disappear when kill solr app. suspect has leak. app somehow holds files , doesn't release them long it's alive? reason inevitable oom error? how can avoid having more , more of files?

thanks!


Comments

Popular posts from this blog

python Tkinter Capturing keyboard events save as one single string -

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

javascript - Z-index in d3.js -