SolrCloud - Jetty vs Tomcat

Question

We're looking to use SolrCloud with separate ZooKeeper instances but need some advice. Our situation is - multiple collections, each with multiple shard's running on Ubuntu 13, Solr 4.7.0, separate ZooKeeper 3.4.5, OpenJDK 7 in AWS

• Jetty or Tomcat? Jetty is built in and requires less config but unless specifying "nohup" the SolrCloud instance exits when you exit the java command running SolrCloud or when you disconnect the SSH session. In addition, it doesn't run as a service out of the box so there's extra config to get it to startup with the server.

Cheers

Answer 1

Agreed that Jetty is the right way to go, but ended up going with the below style solution:

daemon for solr

Answer 2

I would recommend Jetty. As this is what comes bundled, that is what use most commiters and all the testing suite, so it is generally recommended.

You can easily set it up as a service, I have used at least two methods in the past:

• using runit, as described here
• using yajsw: this is what I use now, cross platform (so you can use it on windows too, for the odd installation that needs windows). It's an opensource implementation of the well known Java Service Wrapper.