lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Morissette (JIRA)" <>
Subject [jira] [Commented] (SOLR-11508) Make coreRootDirectory configurable via an environment variable (SOLR_CORE_HOME)
Date Tue, 05 Dec 2017 01:13:00 GMT


Marc Morissette commented on SOLR-11508:

[~elyograg] This is an interesting idea but I'm not sure how this solves the problem. It would
be nice if Solr could start without solr.xml but it would condemn cloud mode users to choose
between sticking to the default settings or mixing their configuration and data. 

It's either that or we would need to externalize every configuration parameter available in
solr.xml (and there are a lot).

> Make coreRootDirectory configurable via an environment variable (SOLR_CORE_HOME)
> --------------------------------------------------------------------------------
>                 Key: SOLR-11508
>                 URL:
>             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
(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
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

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

View raw message