[
https://issues.apache.org/jira/browse/SOLR-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274384#comment-16274384
]
Jan Høydahl commented on SOLR-11508:
------------------------------------
As the one who committed the {{SOLR_DATA_HOME}} feature in the first place, the
intent of that feature was to have *one* place to define which path (mount
point) the index should be located, so you can keep code/config/data separate,
and keep code R/O. You don't need to mess with each single core.property file
or solrconfig.xml file, and it works both for standalone node and SolrCloud.
Core discovery is a remnant from the past that I hope will go away completely,
so +1 for deprecating it along with {{coreRootDirectory}} and get rid of it.
Now, until core discovery dies, I see the two viewpoints as to whether
core.properties belongs with the index or belongs in SOLR_HOME. I always
thought of it as config and explicitly tested for having these in SOLR_HOME.
Also since core discovery is only(?) used in standalone mode you will have your
core configs in SOLR_HOME already, and the discovery mechanisms detects the
core directory by the presence of the {{core.properties}} file, so it makes
sense in my head that the two are co-located. Then, if you wish to move data to
a separate disk, you change {{SOLR_DATA_HOME}} and copy only the data folders
to the new disk. If you want data and config together on an external location,
all you need to change is SOLR_HOME, not SOLR_DATA_HOME.
As to docker, I also believe that the official docker image should use the
official {{install_solr_service.sh}} script, and set a custom SOLR_DATA_HOME,
see SOLR-10906 for plan for installer script to support modifying data home.
> core.properties should be stored $solr.data.home/$core.name
> -----------------------------------------------------------
>
> 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
>
> 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 where running Solr
> in Docker where data must be stored in a directory which is independent from
> the rest of the container.
> Unfortunately, while core data is stored in
> {{$\{solr.data.home}/$\{core.name}/index/...}}, core.properties is stored in
> {{$\{solr.solr.home}/$\{core.name}/core.properties}}.
> Reading SOLR-6671 comments, I think this was the expected behaviour but I
> don't think it is the correct one.
> In addition to being inelegant and counterintuitive, this has the drawback of
> stripping a core of its metadata and breaking core discovery when a Solr
> installation is redeployed, whether in Docker or not.
> core.properties is mostly metadata and although it contains some
> configuration, this configuration is specific to the core it accompanies. I
> believe it should be stored in solr.data.home, with the rest of the data it
> describes.
--
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
