I wasn't part of the original decision either. That said, this will be an uphill battle, for reasons other than "which is better". If we're going to consider major surgery at that level, we've been talking about ripping out Jetty completely and going with Netty or similar. That notion has stalled, largely due to the amount of work it would entail, Jetty-isms are deeply embedded in, for instance, the test framework for.
Plus, the way Solr is used would anyone notice? There's not much exposure as far as _users_ are concerned when it comes to this, it's considered an implementation detail. So in order to be acted upon, the advantages would have to be compelling to justify the work. It's a far larger task than than just substituting one for the other so needs _really_ compelling reasons to happen. I don't personally have much skin in this game, mostly making you aware of a couple of the project-level issues you'll be facing during the discussion. Best, Erick On Fri, Oct 12, 2018 at 4:23 PM Shawn Heisey <[email protected]> wrote: > > On 10/12/2018 2:30 PM, Christopher Schultz wrote: > >> I think the primary reason is that Jetty is more lightweight than > >> Tomcat. > > I think this is more of a perception than actual truth. > > That seems like a very real possibility. > > >> 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. > > When you consider "footprint", do you mean on-disk or in-memory? > > Memory, code, download size. When it comes to disk usage, a few extra > megabytes is peanuts. Most indexes that people build with Solr will be > larger than the program installation -- disk usage isn't something I > worry about. > > And even the footprint thing could be a matter of perception as well, > especially if we can embed the container and have a high degree of > control over exactly what code gets used. > > Convince us with concrete evidence that Tomcat will have a positive > impact on Solr, and that the benefit will be worth the effort involved > in switching. If you can do that, then point us at resources to ease > that switch. > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
