[
https://issues.apache.org/jira/browse/SOLR-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273577#comment-16273577
]
Marc Morissette edited comment on SOLR-11508 at 11/30/17 10:47 PM:
-------------------------------------------------------------------
As to Erick's question, I believe:
* solr.solr.home contains the server-wide config i.e. solr.xml and the
configsets.
* coreRootDirectory is where core discovery happens. It contains the
core.properties files and conf directories. Defaults to solr.solr.home.
* solr.data.home is where core data is stored. It's a directory structure that
is completely parallel to the one that contains the core.properties (see Core
Discovery documentation). Defaults to coreRootDirectory.
The issue here is that the doc says:
{quote} -t <dir> Sets the solr.data.home system property, where Solr will
store data (index).
If not set, Solr uses solr.solr.home for config and
data.{quote}
The doc suggests that the core config will be stored in the directory indicated
by -t. It's currently not the case but I think it should be.
coreRootDirectory has been there for a long time because it makes sense for
people to want to store their cores away from their server configuration (1).
solr.data.home addresses what I think might be a less popular requirement: to
store core config away from core data (2).
The problem is that since 7.0, the command line options and defaults now make
it quite easy to think you're addressing need (1) when you're in reality
configuring for need (2).
was (Author: marc.morissette):
As to Erick's question, I believe:
* solr.solr.home contains the server config i.e. solr.xml and the configsets
* coreRootDirectory is where core discovery happens. It contains the
core.properties files and conf directories. Defaults to solr.solr.home.
* solr.data.home is where the core data is stored. It's a directory structure
that is parallel to the one that contains the core.properties. Defaults to
coreRootDirectory.
> 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: [email protected]
For additional commands, e-mail: [email protected]
