[
https://issues.apache.org/jira/browse/SOLR-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277818#comment-16277818
]
Shawn Heisey commented on SOLR-11508:
-------------------------------------
I'm starting to get an idea of the problem that you want to solve.
What do you think of altering my proposal in one small way: Making sure that
Solr starts even if solr.xml cannot be found. This would allow you to point
solr.solr.home to a location that's completely empty and still have Solr start.
You would then have the option of adding a solr.xml if you desired some
changes there, and even adding configsets if you wanted to run Solr in
standalone mode but still have common configs like SolrCloud.
I did try starting Solr 7.0.0 (already had it downloaded) without a solr.xml,
and it refuses to start. I think this is not how it should behave. Having
Solr log a warning (and possibly even output a message to the console)
mentioning the missing solr.xml would be a good idea. I created a minimal
solr.xml (just contained <solr/> on one line) and Solr did start, so it's not
like it must have any config there.
I have noticed that the stock solr.xml included with 7.x has a lot of config in
it that uses various system properties, with defaults. I have no idea whether
the default settings for these things is reasonable or not. We would need to
make sure that the defaults are reasonable.
> Make coreRootDirectory configurable via an environment variable
> (SOLR_CORE_HOME)
> --------------------------------------------------------------------------------
>
> Key: SOLR-11508
> URL: https://issues.apache.org/jira/browse/SOLR-11508
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Marc Morissette
>
> (Heavily edited)
> Since Solr 7, it is possible to store Solr cores in separate disk locations
> using solr.data.home (see SOLR-6671). This is very useful when running Solr
> in Docker where data must be stored in a directory which is independent from
> the rest of the container.
> While this works well in standalone mode, it doesn't in Cloud mode as the
> core.properties automatically created by Solr are still stored in
> coreRootDirectory and cores created that way disappear when the Solr Docker
> container is redeployed.
> The solution is to configure coreRootDirectory to an empty directory that can
> be mounted outside the Docker container.
> The incoming patch makes this easier to do by allowing coreRootDirectory to
> be configured via a solr.core.home system property and SOLR_CORE_HOME
> environment variable.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
