[jira] [Commented] (SOLR-4907) Discuss and create instructions for taking Solr from the example to robust multi-server production
[ https://issues.apache.org/jira/browse/SOLR-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489706#comment-15489706 ] Jan Høydahl commented on SOLR-4907: --- But if we support prm/deb formats, will we not also need to support *upgrade* of Solr in a more intelligent way, so search don't break after an upgrade due to deprecated APIs. Or would we publish solr5, solr6, solr7 etc, so that people would get automatic minor (compatible) upgrades, but need to do a manual install for the next major version? > 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 > Attachments: SOLR-4907-install.sh > > > There are no good step-by-step instructions for taking the Solr example and > producing a robust production setup on multiple servers. -- 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
[jira] [Commented] (SOLR-4907) Discuss and create instructions for taking Solr from the example to robust multi-server production
[ https://issues.apache.org/jira/browse/SOLR-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489470#comment-15489470 ] Steve Davids commented on SOLR-4907: Thanks, I just updated the repo to move solr.in.sh to /etc/default/. In an ideal world the current Lucene/Solr build system would be modernized a bit (LUCENE-5755) and would then allow you to build the RPM + DEB packages along with the ZIP and TAR files which would all be uploaded to the mirrors with a standard release. The nice thing with using a native package installer is that clients can easily uninstall the package if they don't want it and during upgrades old items are cleaned up and removed appropriately since all of the files are being tracked. I personally think it's just one less barrier to entry and much more natural than: `wget http://apache.claz.org/lucene/solr/6.2.0/solr-6.2.0-src.tgz && tar xzf solr-6.2.0.tgz solr-6.2.0/bin/install_solr_service.sh --strip-components=2`. > 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 > Attachments: SOLR-4907-install.sh > > > There are no good step-by-step instructions for taking the Solr example and > producing a robust production setup on multiple servers. -- 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
[jira] [Commented] (SOLR-4907) Discuss and create instructions for taking Solr from the example to robust multi-server production
[
https://issues.apache.org/jira/browse/SOLR-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488670#comment-15488670
]
Jan Høydahl commented on SOLR-4907:
---
There has since been a change in SOLR-8101 where {{solr.in.sh}} is moved to
{{/etc/default/}}.
Do you have an idea of how we could get such packages included in the disto's?
Who would do the work after each release? Do people see a benefit in having an
{{apt-get install solr}} command available on e.g. Ubuntu?
> 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
> Attachments: SOLR-4907-install.sh
>
>
> There are no good step-by-step instructions for taking the Solr example and
> producing a robust production setup on multiple servers.
--
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
[jira] [Commented] (SOLR-4907) Discuss and create instructions for taking Solr from the example to robust multi-server production
[ https://issues.apache.org/jira/browse/SOLR-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619695#comment-14619695 ] Steve Davids commented on SOLR-4907: I created a Solr RPM (yum) and DEB (apt-get) package builder here: https://github.com/sdavids13/solr-os-packager. It would be great if those packages can be built and pushed out with new Solr releases to make life a bit easier for clients to install and update to newer versions of Solr. The real meat is happening in the Gradle build file which uses Netflix's gradle-os-package plugin: https://github.com/sdavids13/solr-os-packager/blob/master/build.gradle. > 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 > Attachments: SOLR-4907-install.sh > > > There are no good step-by-step instructions for taking the Solr example and > producing a robust production setup on multiple servers. -- 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
[jira] [Commented] (SOLR-4907) Discuss and create instructions for taking Solr from the example to robust multi-server production
[
https://issues.apache.org/jira/browse/SOLR-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678816#comment-13678816
]
Robert Muir commented on SOLR-4907:
---
{quote}
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.
{quote}
I would prefer we leave this as something for downstream packaging maintainers
to do instead. Otherwise, how can we maintain and test all this stuff? I don't
think an answer of 'release manager does it' is a good one here.
If someone is really inspired to e.g. ensure that Ubuntu has robust support,
then isn't it better to contribute directly to them, so that it just works via
the natural methods of installing packages like 'apt-get'?
> 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
> Attachments: SOLR-4907-install.sh
>
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4907) Discuss and create instructions for taking Solr from the example to robust multi-server production
[ https://issues.apache.org/jira/browse/SOLR-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678299#comment-13678299 ] jm commented on SOLR-4907: -- Ok, I attached my installation file, I already warned its possible sub-par. Some notes: 1. I run this as root 2. it uses a project.solr.zip (that contains sorlconfig.xml etc) and a build.xml to overwrite default files that come with the example. It also moves some dir around, renames etc, in order to set a layout of dirs I like. 3. some stuff is needed cause I develop on windows (like fromdos) 4. yajsw is LGPL > 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 > Attachments: SOLR-4907-install.sh > > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4907) Discuss and create instructions for taking Solr from the example to robust multi-server production
[ 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4907) Discuss and create instructions for taking Solr from the example to robust multi-server production
[ https://issues.apache.org/jira/browse/SOLR-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677989#comment-13677989 ] jm commented on SOLR-4907: -- Ok, I had a look at my script...I have not touched it in some months so I didnt remember the details. What I do is: - using Ant, create a zip of custom stuff for current installation (conf files) - deploy a sh on the server, that: - install dependencies (java, ant...) - downloads solr - downloads yajsw - install both - downloads the zip I built for this installation - run ant target that deploys the zip, and removes other dirs/files that I'm not using. Also configures yajsw - start service and check starts fine So I am not sure a pure sh solution would be preferred instead of depending on ant... > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4907) Discuss and create instructions for taking Solr from the example to robust multi-server production
[ https://issues.apache.org/jira/browse/SOLR-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677974#comment-13677974 ] Erick Erickson commented on SOLR-4907: -- jm: Not a problem, just note whatever reservations you have. Anyone picking up on this can just ignore it if they want. You'll see patches put up with "nocommit" in comments, patches that don't compile etc. that are all considered works in progress. It's likely, even if someone is starting from scratch, they'll look over your approach and say "Wow! I didn't think of that, I'll have to do something to take care of that case."... > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4907) Discuss and create instructions for taking Solr from the example to robust multi-server production
[ https://issues.apache.org/jira/browse/SOLR-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677967#comment-13677967 ] jm commented on SOLR-4907: -- Erick, I am not sure how helpful my script would be, it is very targeted to the way I install solr, and OTOH my unix skills are not too sharp and I might be doing stupid/less than optimal things. Other than that I would have no issue sharing it. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4907) Discuss and create instructions for taking Solr from the example to robust multi-server production
[ https://issues.apache.org/jira/browse/SOLR-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677953#comment-13677953 ] Erick Erickson commented on SOLR-4907: -- jm: Yonik's Law Of Patches reads: "A half-baked patch in Jira, with no documentation, no tests and no backwards compatibility is better than no patch at all." So if you can share your install script that would be a great help, you've probably had to work through a bunch of issues creating it that would help anyone picking up on this JIRA. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4907) Discuss and create instructions for taking Solr from the example to robust multi-server production
[ https://issues.apache.org/jira/browse/SOLR-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677889#comment-13677889 ] jm commented on SOLR-4907: -- Just a comment in case it's useful, I always install solr service with http://yajsw.sourceforge.net/ whether it's Windows/Linux (yajsw supports other unixes too but I have not used it myself there). Regarding a batch to properly install Solr, this would be helpful. I currently use one that does this, but I bet one included by Solr but do things much better regarding permissions etc. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4907) Discuss and create instructions for taking Solr from the example to robust multi-server production
[ https://issues.apache.org/jira/browse/SOLR-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677743#comment-13677743 ] Shawn Heisey commented on SOLR-4907: As we create and tweak said instructions, we may discover that the example directory layout needs some changes. Installation scripts would be an awesome thing. If it's possible without gymnastics, we should have a batch file that someone could use (possibly with a user-downloaded copy of SRVANY) to install the example jetty as a Windows service. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
