Right, that's the most common reason to run multiple JVMs. You must be running multiple replicas on each box though to make that viable. By running say 2 JVMS, you're essentially going from hosting, say, 4 replicas in one JVM to 2 replicas in each of 2 JVMs.
You'll incur some overhead due to the second instance of Java running, but that's usually negligible. There's no reason at all to run an independent Jetty, just use the startup scripts to specify a second port as outlined above. If you use the startup script and specify the -e cloud example (on your local box, say), go ahead and specify two instances of Solr. The script will echo out the exact command used to start them up and you can use that as an example. Best, Erick On Mon, Jan 4, 2016 at 8:16 AM, philippa griggs <philippa.gri...@hotmail.co.uk> wrote: > We store a huge amount of data across 10 shards and are getting to a point > where we keep having to up the heap to stop solr from crashing. We are > trying to keep the heap size down, and plan to to host multiple solr > instances on each server which will have a much smaller heap size. > ________________________________________ > From: Mugeesh Husain <muge...@gmail.com> > Sent: 04 January 2016 16:01 > To: solr-user@lucene.apache.org > Subject: Re: Multiple solr instances on one server > > you could use inbuilt(internal) jetty in the production, its depend on > requirement. > > if you want to use other container, tomcat would be the best. > > Elaborate your requirement Please why you want to use multiple instance in a > single server ? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Multiple-solr-instances-on-one-server-tp4248411p4248429.html > Sent from the Solr - User mailing list archive at Nabble.com.
