[
https://issues.apache.org/jira/browse/SOLR-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678052#comment-13678052
]
Shawn Heisey commented on SOLR-4907:
------------------------------------
[~jmlucjav] I agree with Erick, having your script available would be helpful.
Even if it never makes it into the final patch, it can serve as inspiration.
Since it's probably named 'build.xml' you could attach it as
SOLR-4907-ant-install.xml.
On Linux, I have a pretty good init script for older RPM based systems like
RHEL/CentOS. It does need some work to make it more generic and make sure it's
bulletproof. I believe it would also work on newer Fedora systems that use
systemd. It would be easy to adapt to Debian, but I believe that the latest
Ubuntu is using upstart, and I have zero knowledge of what to do there.
Hopefully we could find kind souls willing to work on scripts for Solaris, AIX,
and other big iron systems.
Exactly what to do for Windows is a bit of a sticky point. If we can find a
wrapper whose license allows us to include it, should we do so, or would it be
better to ask the user to download one that we support, regardless of the
licensing? I personally use Windows as a client, but avoid using it as a
server.
> Discuss and create instructions for taking Solr from the example to robust
> multi-server production
> --------------------------------------------------------------------------------------------------
>
> Key: SOLR-4907
> URL: https://issues.apache.org/jira/browse/SOLR-4907
> Project: Solr
> Issue Type: Improvement
> Reporter: Shawn Heisey
>
> There are no good step-by-step instructions for taking the Solr example and
> producing a robust production setup on multiple servers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]