lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SOLR-3613) Namespace Solr's JAVA OPTIONS
Date Wed, 11 Jul 2012 20:33:34 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411961#comment-13411961
] 

Jan Høydahl commented on SOLR-3613:
-----------------------------------

bq. Would it be controversial to change this to say Jetty instead? Because Tomcat is completely
untested, may not even work, etc,

Supporting only Jetty? We shouldn't go there. Not supporting other app-servers is going backwards.
The customers of aforementioned Escenic Content Studio (and other applications embedding Solr)
can freely choose what app-server to run their online newspaper on ([http://en.wikipedia.org/wiki/Escenic]).
Do you want them to stop using Solr because we "drop" support for anything but Jetty, or force
them and their customers into spinning up a Jetty process alongside their ECM? That sucks.

bq. Most of the use of Solr is in Jetty. Most of the bugs we find at the container level are
around Jetty. We have had to patch the version of Jetty we are using to avoid bugs, upgrade
Jetty to avoid bugs. If you are not using our shipped Jetty, your probably not doing it right
if you ask me.

>From where is that statistics? Most of our customers choose to run Solr in Tomcat, many
use Jetty, some use Resin and yet others use whatever their IT department prefer. In the real
world - when taking about the big installs - each company's IT dept has their preferred app-server
which they know in/out and keep up to date, monitored etc.

bq. Personally, I think if you want to embed Solr, go ahead and use embedded Solr

I thought we more or less had discouraged use of EmbeddedSolr? According to [http://wiki.apache.org/solr/EmbeddedSolr]:
*The simplest, safest, way to use Solr is via Solr's standard HTTP interfaces. Embedding Solr
is less flexible, harder to support, not as well tested, and should be reserved for special
circumstances.*

I think we should ask the broader dev-community and our users what App-servers they use, how
they want to deploy or bundle Solr etc.
                
> Namespace Solr's JAVA OPTIONS
> -----------------------------
>
>                 Key: SOLR-3613
>                 URL: https://issues.apache.org/jira/browse/SOLR-3613
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 4.0-ALPHA
>            Reporter: Jan Høydahl
>             Fix For: 4.0
>
>
> Solr being a web-app, should play nicely in a setting where users deploy it on a shared
appServer.
> To this regard Solr's JAVA_OPTS should be properly name spaced, both to avoid name clashes
and for clarity when reading your appserver startup script. We currently do that with most:
{{solr.solr.home, solr.data.dir, solr.abortOnConfigurationError, solr.directoryFactory, solr.clustering.enabled,
solr.velocity.enabled etc}}, but for some opts we fail to do so.
> Before release of 4.0 we should make sure to clean this up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message