Actually, just use the new bin/solr start scripts and ignore whether it's running Jetty under the covers or not I think.
Best, Erick On Mon, May 25, 2015 at 7:11 PM, Zheng Lin Edwin Yeo <edwinye...@gmail.com> wrote: > Hi Shawn, > > Thanks for your reply. So the recommendation is still to stick with the > Jetty that's included in Solr? > > From what you say, seems that if we use external Jetty, we have to do more > configuration to tune it to fit Solr, and it will probably use more memory > and run slower too.There might also be issues with a future release of Solr. > > > Regards, > Edwin > > > On 25 May 2015 at 21:51, Shawn Heisey <apa...@elyograg.org> wrote: > >> On 5/25/2015 3:28 AM, Zheng Lin Edwin Yeo wrote: >> > I understand that Jetty comes together with the Solr installation >> package, >> > and that by default, Solr uses Jetty internally to power it's HTTP stack. >> > >> > Would like to check, will there be any performance difference when we run >> > the Jetty internally as compared to running an external copy of Jetty? I >> > have heard of source saying that the performance will be better if we run >> > on external copy. Is that true? >> >> The config for the included Jetty has had a small amount of tuning done >> specifically for Solr. You would lose that if you switched. Also, the >> Jetty included with Solr has had a bunch of the jars and their >> configuration stripped out. That makes it use less memory, and likely >> run a little bit faster. >> >> > Also, as support for deploying Solr as a WAR in standalone servlet >> > containers like Jetty is no longer supported from Solr 5.0, is it still >> > possible to deploy Solr using an external copy of Jetty? >> >> Although we don't recommend it, for now you can find the .war file in >> the download and deploy it in other containers. That will be changing >> in a future release, but we don't have an ETA. There is a wiki page >> discussing the situation. It is still a work in progress: >> >> https://wiki.apache.org/solr/WhyNoWar >> >> Thanks, >> Shawn >> >>
