lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] [Commented] (SOLR-3613) Namespace Solr's JAVA OPTIONS
Date Wed, 11 Jul 2012 19:44:35 GMT


Mark Miller commented on SOLR-3613:

Forgot to mention in my pro using shipped jetty list:

We also configure jetty for the best Solr experience. Raising max threads and so on.
We also doc jetty better, and can have better doc about where to go to enable ssl, or this
or that. Over time, a single emphasis will provide better doc and a better experience if you
are using whats doc'd (even if a lot of the doc is us referencing into jetty docs for specific

Having one thing to support and tweak is surely better than a range of things?

By telling people they should feel free to run our Solr webapp anywhere, we are saying, go,
have a poor experience with Solr in comparison to using what we ship. I'd rather optimize
the out of the box experience, claim that is the recommended experience, and then say, hey,
it's open source - if you want to make this all work with tomcat, its probably doable, do
what you want. But Solr is shipped as an app rather than some WAR from 1998.
> Namespace Solr's JAVA OPTIONS
> -----------------------------
>                 Key: SOLR-3613
>                 URL:
>             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
> 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.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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message