One more thing. I don't think this was mentioned, but you can: - optimize your indices - use compound index format
That will lower the number of open file handles. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: vivek sar <vivex...@gmail.com> > To: solr-user@lucene.apache.org > Sent: Friday, April 10, 2009 5:59:37 PM > Subject: Re: Question on StreamingUpdateSolrServer > > I also noticed that the Solr app has over 6000 file handles open - > > "lsof | grep solr | wc -l" - shows 6455 > > I've 10 cores (using multi-core) managed by the same Solr instance. As > soon as start up the Tomcat the open file count goes up to 6400. Few > questions, > > 1) Why is Solr holding on to all the segments from all the cores - is > it because of auto-warmer? > 2) How can I reduce the open file count? > 3) Is there a way to stop the auto-warmer? > 4) Could this be related to "Tomcat returning blank page for every request"? > > Any ideas? > > Thanks, > -vivek > > On Fri, Apr 10, 2009 at 1:48 PM, vivek sar wrote: > > Hi, > > > > I was using CommonsHttpSolrServer for indexing, but having two > > threads writing (10K batches) at the same time was throwing, > > > > "ProtocolException: Unbuffered entity enclosing request can not be > > repeated. > " > > > > I switched to StreamingUpdateSolrServer (using addBeans) and I don't > > see the problem anymore. The speed is very fast - getting around > > 25k/sec (single thread), but I'm facing another problem. When the > > indexer using StreamingUpdateSolrServer is running I'm not able to > > send any url request from browser to Solr web app. I just get blank > > page. I can't even get to the admin interface. I'm also not able to > > shutdown the Tomcat running the Solr webapp when the Indexer is > > running. I've to first stop the Indexer app and then stop the Tomcat. > > I don't have this problem when using CommonsHttpSolrServer. > > > > Here is how I'm creating it, > > > > server = new StreamingUpdateSolrServer(url, 1000,3); > > > > I simply call server.addBeans(...) on it. Is there anything else I > > need to do to make use of StreamingUpdateSolrServer? Why does Tomcat > > become unresponsive when Indexer using StreamingUpdateSolrServer is > > running (though, indexing happens fine)? > > > > Thanks, > > -vivek > >
