On 19-Oct-07, at 7:19 AM, Ed Summers wrote:
On 10/18/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
I realize this is a bit off-topic -- but I'm curious what the
rationale was behind having that many solr instances on that many
machines and how they are coordinated. Is it a master/slave setup or
a
On 10/18/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
> I have a large number of servers, each running 1-2 containers, each
> having 1-2 solr deployments (fixed). If I want a new Solr instance,
> I just start a new container (possibly on a new server). I treat it
> like a process, and can shut it do
On 18-Oct-07, at 1:01 PM, Stu Hood wrote:
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?
I have a large number of servers, each running
@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
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
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 othe
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-use