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-11508) Make coreRootDirectory configurable via an environment variable (SOLR_CORE_HOME)
Date Wed, 06 Dec 2017 16:04:00 GMT

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

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

I still don't get it. What benefit exactly would a "rename" of {{solr.data.home}} to {{solr.index.home}}
give? What would be the difference between current 7.2 {{solr.data.home}} and your new {{solr.index.home}}?

Sounds like a lot of confusion could be handled with some documentation patches (describe
SOLR_DATA_HOME mainly in context of standalone mode), and code changes to *not* require {{solr.xml}}
or {{zoo.cfg}} files in {{SOLR_HOME}} at all.

Then Cloud users would separate code/config/data by installing binaries in a R/O {{/opt/solr}},
keep all config in Zookeeper, even {{solr.xml}}, and then point SOLR_HOME to some writeable
location of choice (just as they have always done in all Solr versions).

Standalone users can choose to separate code from config+data by having R/O binaries in {{/opt/solr}},
and choose a writeable SOLR_HOME ({{/var/solr/home}}) for core config and data, just as they
have always done in all Solr versions. If they in addition want to separate data from config,
they must configure SOLR_DATA_HOME  (e.g. {{/mnt/largeDisk/solr-data}}) in addition, this
is because standalone users store their config locally on disk.

Both of these scenarios will work on Docker if we do not require any pre-existing files in
SOLR_HOME?

> 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