This is good to know, and I find it welcome advice; I would recommend
making sure this advice is clearly highlighted in the relevant Solr
docs, such as any getting started docs.
I'm not sure everyone realizes this, and some go down tomcat route
without realizing the Solr committers recommend jetty -- or use a stock
jetty without realizing the 'example' jetty is recommended and actually
intended to be used by Solr users in production! I think it's easy to
not catch this advice.
On 10/20/13 5:55 PM, Shawn Heisey wrote:
On 10/20/2013 2:57 PM, Shawn Heisey wrote:
We recommend jetty. The solr example uses jetty.
I have a clarification for this statement. We actually recommend using
the jetty that's included in the Solr 4.x example. It is stripped of
all unnecessary features and its config has had some minor tuning so
it's optimized for Solr. The jetty binaries in 4.x are completely
unmodified from the upstream download, we just don't include all of
them. On the 1.x and 3.x examples, there was a small bug in Jetty 6, so
those versions included modified binaries.
If you download jetty from eclipse.org or install it from your operating
system's repository, it will include components you don't need and its
config won't be optimized for Solr, but it will still be a lot closer to
what's actually tested than tomcat is.
Thanks,
Shawn
