lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Morissette (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-11508) Make coreRootDirectory configurable via an environment variable (SOLR_CORE_HOME)
Date Mon, 04 Dec 2017 19:43:00 GMT

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

Marc Morissette commented on SOLR-11508:
----------------------------------------

I've started work on a patch that adds the ability to set coreRootDirectory via an environment
variable and command line option: https://github.com/morissm/lucene-solr/commit/95cbd1410fb4bdf97fd9ffec8737117a7931054d

I'm starting to have second thoughts though. Solr already has a steep learning curve and I'm
loathe to add yet another option if there is a way to avoid it.

What if core.properties files were stored in SOLR_DATA_HOME only when Solr is in cloud mode?
Unless I'm mistaken, all configuration is stored in Zookeeper in cloud mode so that is the
only file that matters. As I've argued earlier, core.properties files in cloud mode are mostly
an implementation detail and belong with the data. 

The only issue would be how to handle the transition for people who have set SOLR_DATA_HOME
in cloud mode pre 7.2. I've thought of many automated ways to handle the transition but this
might not be easy to accomplish without introducing some potential unintended behaviours.

Comments?

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message