On 2/4/2016 7:29 AM, Shahzad Masud wrote: > Q: Is this a normal that one node support one shard in Jetty? > Q: Can anyone point to appropriate guideline; if jetty is better than > tomcat? > Q: Have anyone else experienced similar migration, and concluded that > tomcat is better.
Solr 5.x is more difficult to put into Tomcat than 4.x was -- there is no .war file in the download at all as of version 5.3. It can still be done, but we strongly recommend using Solr as it is shipped, with Jetty. https://wiki.apache.org/solr/WhyNoWar The recommendation is to use the Jetty that comes with Solr, not a separate Jetty package. I would not be too surprised to learn that Tomcat is better than a separate Jetty package, but in that case, both of them have no tuning. The jetty that comes with Solr is tuned for Solr. The most important part of that tuning is the maxThreads setting -- the default value of 200 in Tomcat and Jetty is easy to exceed ... and when the container starts limiting the number of threads, performance *will* suffer. No matter where the Jetty comes from, there is *NOT* a limitation of one shard per node with Jetty. Where did you hear that? Whatever resource you are looking at which states this is wrong, and I'd like to get it corrected. I personally am running Solr installs (both 4.x and 5.x) on Jetty which have dozens of cores (shards). FYI -- SolrCloud fully supports sharded indexes. Sharding is often the entire point of using SolrCloud. Sharded indexes are easier to manage in SolrCloud than they are in standalone mode -- shard handling for both indexing and queries is fully automated. Thanks, Shawn
