The use case is to prevent the necessity to download something else
(zookeeper) when everything needed to run it is (likely) present in the
Solr distribution already.
Maybe we don't need to start Jetty, maybe we can start Zookeeper with an
extra script in the Solr codebase.
At present, if you are
Curious what the use case is for this? Zookeeper is not an HTTP
service so loading it in Jetty by itself doesn't really make sense. I
also think this creates more work for the Solr team especially since
setting up a production ensemble shouldn't take more than a few
minutes once you have the nodes
Assumptions:
* you currently have two choices to start Zookeeper: run it embedded
within Solr, or download it from the ZooKeeper site and start it
independently.
* everything you need to run ZooKeeper (embedded or not) is included
within the Solr distribution
Assuming I've got the above righ
