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 unfamiliar with ZooKeeper, getting it up and running can be a challenge (I've seen quite a few people fail at it during training scenarios). Upayavira On Tue, Jul 23, 2013, at 03:21 PM, Timothy Potter wrote: > 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 provisioned. > > On Tue, Jul 23, 2013 at 7:05 AM, Upayavira <u...@odoko.co.uk> wrote: > > 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 right, then currently starting an embedded > > ZooKeeper is easy (-DzkRun), and starting an ensemble is irritatingly > > complex. > > > > So, my question is, how hard would it be to start Zookeeper without > > Solr, but from within the Solr codebase? -DensembleOnly or some such, > > causes Solr not to load, but Zookeeper still starts. I'm assuming that > > Jetty would still listen on port 8983, but it wouldn't initialise the > > Solr webapp: > > > > java -DzkRun -DzkEnsembleOnly > > -DzkHosts=zkhost01:9983,zkhost02:9983,zkhost03:9983 -jar start.jar > > > > Is this possible? If it is, I'm happy to have a go at making it happen. > > > > Upayavira > > > >
