Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Wed, 20 Aug 2014 02:55:20 +0000 (UTC)
From: "Timothy Potter (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12598537.1342094102943.39494.1408503320291@arcas>
In-Reply-To: <JIRA.12598537.1342094102943@arcas>
References: <JIRA.12598537.1342094102943@arcas>
Subject: [jira] [Updated] (SOLR-3617) Consider adding start scripts.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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

Here's an updated patch. Hoping to backport this to 4x (for inclusion in 4.10) unless anyone has any major concerns over the approach. This patch includes some minor bug fixes found by our QA team and some hardening of command-line parsing. Also improved the interactive SolrCloud example session to prompt the user for a configuration name, either default or schemaless.

> 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, 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