I'm running SVN r583865 (1.3-dev). Mike: when you say 'process level management', do you mean starting them statically? Or starting them dynamically, but using a different container for each instance?
A little explanation is probably in order: ------ We're using Solr to provide log search capability to our customer service department. We keep 7 days of logs available by starting up a new instance every 6 hours or so and stopping the oldest instance. We merge in pre-indexed logs every 10 minutes. We have a few nodes providing search, so we have one machine that schedules Solr instances on the nodes with Tomcat Manager, and all instances are searched simultaneously using the patch from SOLR-303. An option I'm considering is keeping a static number of instances on each node, and doing a id[* TO *] delete when an instance needs to be reused, but I'd rather figure this bug out than refactor the scheduling/merging code for static instances. Java ought to be able to GC its way out of situations like this... Thanks, Stu -----Original Message----- From: Tom Hill <[EMAIL PROTECTED]> Sent: Thursday, October 18, 2007 3:34pm To: solr-user@lucene.apache.org Subject: Re: Solr + Tomcat Undeploy Leaks I certainly have seen memory problems when I just drop a new war file in place. So now I usually stop tomcat and restart. I used to see problems (pre-1.0) when I just redeployed repeatedly, without even accessing the app, but I've got a little script running in the background that has done that 50 times now, without running out of space. Are you on a current version? I'm on 12 Tlom On 10/18/07, Mike Klaas <[EMAIL PROTECTED]> wrote: > > I'm not sure that many people are dynamically taking down/starting up > Solr webapps in servlet containers. I certainly perfer process-level > management of my (many) Solr instances. > > -Mike > > On 18-Oct-07, at 10:40 AM, Stu Hood wrote: > > > Any ideas? > > > > Has anyone had experienced this problem with other containers? I'm > > not tied to Tomcat if I can find another servlet host with a REST > > api for deploying apps. > > > > Thanks, > > Stu > > > > -----Original Message----- > > From: Stu Hood <[EMAIL PROTECTED]> > > Sent: Wednesday, October 17, 2007 4:46pm > > To: solr-user@lucene.apache.org > > Subject: Solr + Tomcat Undeploy Leaks > > > > Hello, > > > > I'm using the Tomcat Manager app with 6.0.14 to start and stop Solr > > instances, and I believe I am running into a variant of the linked > > issue: > > > > http://wiki.apache.org/jakarta-commons/Logging/UndeployMemoryLeak? > > action=print > > > > According to `top`, the 'size' of the Tomcat process reaches the > > limit I have set for it with the Java -Xmx flag soon after starting > > and launching a few instances. The 'RSS' varies based on how full > > the caches are at any particular time, but I don't think it ever > > reaches the 'size'. > > > > After a few days, I will get OOM errors in the logs when I try and > > start new instances (note: this is typically in the middle of the > > night, when usage is low), and all of the instances will stop > > responding until I (hard) restart Tomcat. > > > > ------------------------ > > > > Has anyone run into this issue before? Is logging the culprit? If > > so, what options do I have (besides setting up a cron job to > > restart Tomcat nightly...) > > > > Thanks, > > > > Stu Hood > > Webmail.us > > "You manage your business. We'll manage your email."(R) > > > > > > > >