I have been running Solr 4.10 with Tomcat 7 with manual shard scheme (i.e.
4 Tomcats with 16 shards - Each tomcat having 4 contexts / instances in it
to represent shards). It was working fairly good for last 4 years, but with
few OOM (Out of memory) on random servers. This situation get back normal,
if I schedule a random server restart. I have been using distributed search
feature; which disallow me to use Solr Cloud.

Each shard is pointing to separate folders. In migration to Jetty; it
appears as a surprise that it support single shard per Jetty server. In
order to test this one further, I created 16 servers for all and bench
mark. Jetty / Solr performance is slow than Tomcat / Solr performance,
which is a surprise. tomcat is 25% faster than jetty. I am sure; I am
missing something otherwise Solr team might not be recommending Jetty for
5.X versions.

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.

Thank you,
Have a great day !

Shahzad

Reply via email to