Shawn Heisey created SOLR-7505:
----------------------------------
Summary: startup scripts - read-only install dir and other
improvements
Key: SOLR-7505
URL: https://issues.apache.org/jira/browse/SOLR-7505
Project: Solr
Issue Type: Improvement
Components: scripts and tools
Affects Versions: 5.1
Reporter: Shawn Heisey
Assignee: Shawn Heisey
Priority: Minor
Talking to a user on IRC, I've come across some things we could do better in
our startup scripts and the documentation around them.
* It's very difficult to make the entire install directory read-only from the
point of view of the RUNAS user.
** The war must be extracted, by default this is done to server/solr-webapp.
** Fixing this will require a few changes to the scripts as well as some
additions to the documentation. I'm not suggesting that we make this a default
setup, just provide information on how a user can accomplish it.
* If SOLR_ENV is pointed at a script that is empty, nonexistent, or only
includes minimal user settings, the settings for default max heap and GC tuning
are lost, and return to undesirable Java defaults. I believe that a user env
file should *supplement* solr.in.{sh,cmd}, not *replace* it. The user can
always completely override the provided defaults in their env file.
There were some other ideas I had, will update if I remember them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
