On Fri, Sep 10, 2010 at 3:24 PM, <karl.wri...@nokia.com> wrote: > Hi Yonik, > > Be that as it may, I'm seeing a steady increase in file handles used by that > process over an extended period of time (now 20+ minutes): > > r...@duck6:~# lsof -p 22379 | wc > 786 7714 108339 > r...@duck6:~# lsof -p 22379 | wc > 787 7723 108469 > r...@duck6:~# lsof -p 22379 | wc > 787 7723 108469 > r...@duck6:~# lsof -p 22379 | wc > 812 7948 111719 > r...@duck6:~# lsof -p 22379 | wc > 816 7984 112239 > r...@duck6:~# lsof -p 22379 | wc > 817 7993 112369 > r...@duck6:~# lsof -p 22379 | wc > 822 8038 113019 > r...@duck6:~# lsof -p 22379 | wc > 847 8308 116719 > r...@duck6:~# lsof -p 22379 | wc > 852 8353 117369 > r...@duck6:~# lsof -p 22379 | wc > 897 8803 123669 > r...@duck6:~# lsof -p 22379 | wc > 1022 10018 140819 > r...@duck6:~# > > This doesn't smell like spiky resource usage to me. It smells like a leak. > ;-)
Or normal growth until a major merge compacts things (as it relates to indexing at least - there may be other things that take up handles). I guess the point is, there's not currently enough info to tell if anything is wrong. I do know for a fact that 1024 has never been enough file handles in the general case for Lucene/Solr and non-compound indexes. -Yonik http://lucenerevolution.org Lucene/Solr Conference, Boston Oct 7-8 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
