What is better container for SOLR: Tomcat or Jetty
Install Prometheus using Helm charts. Install ZooKeeper using kubectl command line tool. Install Solr and Solr metrics exporter using kubectl command line tool. Configure Horizontal Pod Autoscaler and Cluster Autoscaler using kubectl command line tool.
Start the Server If you are running Windows, you can start Solr by running bin\solr. cmd instead. This will start Solr in the background, listening on port 8983. When you start Solr in the background, the script will wait to make sure Solr starts correctly before returning to the command line prompt.
Jetty is bundled with Solr due to it's size:
The Solr example app has Jetty in it just because at the time we set it up, Jetty was the simplest/smallest servlet container we found that could be run easily in a cross platform way (ie: "java -jar start.jar"). That does not imply that Solr runs better under Jetty, or that Jetty is only good enough for demos -- it's just that Jetty made our demo setup easier.
Users should decide for themselves which Servlet Container they consider the easiest/best for their use cases based on their needs/experience. For high traffic scenarios, investing time for tuning the servlet container can often make a big difference.
I have been running Solr with Jetty for few small sites for months and had no problems.
My vote goes for Jetty.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With