[
https://issues.apache.org/jira/browse/SOLR-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274581#comment-16274581
]
Shawn Heisey commented on SOLR-11508:
-------------------------------------
[~dsmiley], You want to get rid of core discovery? I'm showing my age when I
say that for me, the "new" shine of that feature still hasn't quite worn off
(working since 4.4, required since 5.0). What do you want to do instead? Core
discovery is used even in cloud mode, though I think when "zookeeper as truth"
is fully realized, SolrCloud probably won't use it any more, and I support that
idea. For standalone mode, I think it's important, unless you have something
in mind to replace it that most of us can agree is better.
The absolute easiest way to move everything other than code so everything in
the program directory can be read-only is to set the solr home. Technically
speaking, especially with capabilities added later, this is "just" the location
of solr.xml, assuming that file isn't found in zookeeper, though it also gets
used as a starting location for core config and data.
IMHO, coreRootDirectory and solr.data.home are expert options for setting up a
directory structure with more separation than what Solr does by default, and
the documentation should state this. I'm absolutely fine with having these
features -- they give users a lot of control over Solr's index directory
structure.
For most users, the solr home is all they'll need, and I think the
documentation should say that too. The expert options should NOT be in the
stock config files, except perhaps as commented out examples of what the user
*CAN* do, if they're interested in greater control and responsibility.
I think that the names we've got for these options, although technically
correct, are likely confusing to novices. Here's a proposal, intended only for
the master branch:
{quote}
Eliminate either solr.data.home or solr.solr.home, and use whichever is left
for functionality currently handled by solr.solr.home.
Use solr.index.home for functionality currently handled by solr.data.home.
This would be documented as an expert option.
Get rid of coreRootDirectory entirely -- defining the solr home and
solr.index.home effectively gets the same results, which are config and data in
separate places ... and I don't see much value in separating solr.xml from the
rest of the config. For SolrCloud, it could be argued that solr.index.home is
unnecessary, though some might want core.properties to be in a different place
than the indexes. That need goes away if "zookeeper as truth" eliminates core
discovery in cloud mode.
I don't think we should backport these ideas to 7.x -- it's a fairly major
change that would confuse users who already understand what's there, and seems
better to do in a major release.
{quote}
I do agree that the script should support environment variables for configuring
all these options, even the expert ones, and that this should happen in 7.x.
> 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
