[jira] [Updated] (SOLR-3617) Consider adding start scripts.

["Timothy Potter (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Potter updated SOLR-3617:
---------------------------------

    Attachment: SOLR-3617.patch

I've committed this on trunk. Notable improvements from this last patch include:

* Interactive session to launch SolrCloud example for Windows
* bin/solr -i calls the SolrCLI class (SOLR-6233) to get basic information about a running server
* bin/solr healthcheck -collection foo runs some basic health checks against a collection (cloud mode only)
* Support for legacy (branch_4x layout) and soon-to-be server layout (SOLR-3619)
* Windows script works when Solr is installed in a directory containing a space
* Hardening of *nix and Windows scripts

I'm hoping to back-port these to branch_4x soon so they can be included in the 4.10 release.

> Consider adding start scripts.
> ------------------------------
>
>                 Key: SOLR-3617
>                 URL: https://issues.apache.org/jira/browse/SOLR-3617
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Mark Miller
>            Assignee: Timothy Potter
>         Attachments: SOLR-3617.patch, SOLR-3617.patch, SOLR-3617.patch, SOLR-3617.patch
>
>
> I've always found that starting Solr with java -jar start.jar is a little odd if you are not a java guy, but I think there are bigger pros than looking less odd in shipping some start scripts.
> Not only do you get a cleaner start command:
> sh solr.sh or solr.bat or something
> But you also can do a couple other little nice things:
> * it becomes fairly obvious for a new casual user to see how to start the system without reading doc.
> * you can make the working dir the location of the script - this lets you call the start script from another dir and still have all the relative dir setup work.
> * have an out of the box place to save startup params like -Xmx.
> * we could have multiple start scripts - say solr-dev.sh that logged to the console and default to sys default for RAM - and also solr-prod which was fully configured for logging, pegged Xms and Xmx at some larger value (1GB?) etc.
> You would still of course be able to make the java cmd directly - and that is probably what you would do when it's time to run as a service - but these could be good starter scripts to get people on the right track and improve the initial user experience.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org