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) core.properties should be stored $solr.data.home/$core.name
Date Fri, 01 Dec 2017 19:05:00 GMT

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

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

[~elyograg], unfortunately what you propose is not really compatible with Docker. In Docker,
configuration remains part of the image and users customize that configuration by either extending
base images, mapping configuration files during deployment or configuring environment variables.
Data must go in a separate directory, ideally one that can be empty without adverse effects.
SOLR_HOME is thus not a good solution because it contains configsets and solr.xml.

SOLR_DATA_HOME is a good solution for people who use Solr in standalone mode and I will readily
admit my patch addresses this use case poorly. I did not completely understand this variable's
purpose at first and thought it was somehow "wrong" but it's not. I'm not arguing any change
to it anymore.

In Cloud mode however, we deal with collections. Cores are more of an implementation detail.
In Cloud Mode, I'd argue individual core.properties are closer to segment descriptors in their
purpose which is why it makes more sense to keep them with the rest of the data. This is why
I believe coreRootDirectory is the best way to separate configuration from data in Cloud mode.

To summarize, after reading everyone's viewpoint, I believe all 3 configuration variables
are necessary as they address different use cases. [~dsmiley] and I are simply arguing for
an easier way to configure coreRootDirectory. If no one sees an objection to that, I'll change
the description of this bug as it's getting pretty stale and I'll find some time to work on
a new patch to address that.

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


Mime
View raw message