Tomcat should work just fine in most cases. The downside to Tomcat is that all of the devs generally run Jetty since it's the default. Also, all of our units tests run against Jetty - in fact, a specific version of Jetty.
Usually, Solr will run fine in other webapps. Many, many users run Solr in other webapps. All of our tests run against a specific version of Jetty though. In some (generally rare) cases, that means something might work with Jetty and not another container until/unless the issue is reported by a user and fixed. - Mark On Apr 23, 2013, at 3:25 PM, Furkan KAMACI <furkankam...@gmail.com> wrote: > At first I will work on 100 Solr nodes and I want to use Tomcat as > container and deploy Solr as a war. I just wonder what folks are using for > large systems and what kind of problems or benefits they have with their > choices. > > > 2013/3/26 Otis Gospodnetic <otis.gospodne...@gmail.com> > >> Hi, >> >> This question is too open-ended for anyone to give you a good answer. >> Maybe you want to ask more specific questions? As for embedding vs. war, >> start with a simpler war and think about the alternatives if that doesn't >> work for you. >> >> Otis >> -- >> Solr & ElasticSearch Support >> http://sematext.com/ >> >> >> >> >> >> On Fri, Mar 22, 2013 at 8:07 AM, Furkan KAMACI <furkankam...@gmail.com >>> wrote: >> >>> If I want to use Solr in a web search engine what kind of strategies >> should >>> I follow about how to run Solr. I mean I can run it via embedded jetty or >>> use war and deploy to a container? You should consider that I will have >>> heavy work load on my Solr. >>> >>
