Shawn Heisey created SOLR-9590: ---------------------------------- Summary: Service installation -- save breadcrumbs for other scripts to use Key: SOLR-9590 URL: https://issues.apache.org/jira/browse/SOLR-9590 Project: Solr Issue Type: New Feature Security Level: Public (Default Security Level. Issues are Public) Components: scripts and tools Reporter: Shawn Heisey Priority: Minor
When I opened SOLR-7826, I brought up the idea of installation breadcrumbs. If we had good breadcrumb data saved in the install directory by the install script, a number of other scripts could use the breadcrumbs to gather relevant data about the *service* installation, for additional safety and more automatic operation. The "bin/solr create" command could verify that it is running as the exact same user that installed Solr, and abort if they don't match. What if zkcli.sh (and bin/solr zookeeper options) no longer needed to be told where zookeeper was, because it could find its way to /etc/default/<service>.in.sh or $SOLR_HOME/solr.xml and grab zkHost from there? The same thing could happen for zkHost in the idea that I filed as SOLR-9587. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org