On 10/12/2018 1:18 PM, Christopher Schultz wrote:
I'm curious as to why Solr uses Jetty and not Tomcat.
I wasn't part of the project when that decision was made. Jetty was already included with Solr when I first downloaded it -- Solr version 1.4.0, back in 2009. Jetty wasn't quite as integrated as it is now, and at that time, Solr was still shipping as a WAR, suitable for any container.
I'm going to offer my two cents, which I admit up front is only an educated guess. Others can probably give you concrete information about discussions that happened nearly a decade ago.
I think the primary reason is that Jetty is more lightweight than Tomcat. And the Jetty that's included with Solr is considerably stripped down compared to a standard binary distribution, so its footprint is VERY small. Since Solr 4.0 when Solr's UI completely changed to Javascript, even JSP support is missing.
We'd like to make Tomcat such that, if you had the choice to make again, you might pick Tomcat instead.
If you can make a very compelling argument about benefits we would see from moving to Tomcat, and can help us modify things like our testing infrastructure and scripting to make it all work, I see no reason we wouldn't give it serious consideration. It would be VERY important for the test infrastructure to use the same container as the binary distribution. That's probably the biggest source of inertia that keeps us where we are.
Take a look at SOLR-6733 (and its child SOLR-6734) in Jira for some ideas I've been tossing around for embedding the container directly into Solr itself, so that Solr is a standalone application. I never have the time I need to work on it, and it's a really major task. I know from work I've done using Spring Boot that Tomcat can also be embedded.
Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
