Thanks Shalin. The problem is I don't see any error message in the catalina.out. I don't even see the request coming in - I simply get blank page on browser. If I keep trying the request goes through and I get respond from Solr, but then it become unresponsive again or sometimes throws "connection reset" error. I'm not sure why would it work sometimes and not the other times for the same query. As soon as I stop the Indexer process things start working fine. Any way I can debug this problem?
-vivek On Fri, Apr 10, 2009 at 11:05 PM, Shalin Shekhar Mangar <shalinman...@gmail.com> wrote: > On Sat, Apr 11, 2009 at 3:29 AM, vivek sar <vivex...@gmail.com> wrote: > >> 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? > > > You have 10 cores, so Solr opens 10 indexes, each of which contains multiple > files. That is one reason. Apart from that, Tomcat will keep some file > handles for incoming connections. > > >> >> 2) How can I reduce the open file count? > > > Are they causing a problem? Tomcat will log messages when it cannot accept > incoming connections if it runs out of available file handles. But if you > experiencing issues, you can increase the file handle limit or you can set > useCompoundFile=true in solrconfig.xml. > > >> >> 3) Is there a way to stop the auto-warmer? >> 4) Could this be related to "Tomcat returning blank page for every >> request"? >> > > It could be. Check the Tomcat and Solr logs. > > -- > Regards, > Shalin Shekhar Mangar. >
