According to answers here for a huge crawling system and high response time searching SolrCloud system I will try Jetty. If anyone has a good reason they can explain it here, you are right. By the way, Shawn when I read you answer I understand that I should choose embedded Jetty, is that right?
2013/4/23 Shawn Heisey <s...@elyograg.org> > On 4/23/2013 1:52 PM, Furkan KAMACI wrote: > >> Thanks for the answer. If I find something that explains using embedded >> Jetty or Jetty, or Tomcat it would be nice. >> >> 2013/4/23 Mark Miller <markrmil...@gmail.com> >> >> 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 outlines a really good reason to use Jetty - it's extremely well > tested. New tests are being added all the time, and most of those will > start Jetty to run. > > If you don't already have a good reason to use a container other than the > Jetty included in Solr, then go and copy the example setup and modify it > until it does what you need. The one thing that's really missing is an > init script to manage Solr startup and shutdown. I plan to do something > about that, but I've got a lot of cleanup to do on it. > > I've only come across one truly compelling reason to use something else: > If your system admins are already familiar with Tomcat, Glassfish, or > something else, then you probably want to stick with that. For instance, > you may have automation in place for deploying and managing farms of Tomcat > servers. Switching would likely be too painful. > > There could be features useful for Solr in other containers that I don't > know about. If there are, and someone has a good reason for needing those > features, let us know about them. Update the wiki. > > Jetty is a low-overhead servlet container without a lot of fancy features. > The Jetty instance that is included in the Solr example is a bare-bones > setup. It does not include all of the jars or config found in a full Jetty > download, because those features are not needed for Solr. > > Thanks, > Shawn > >
