lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Commented] (SOLR-11508) should be stored $$
Date Fri, 01 Dec 2017 14:07:00 GMT


David Smiley commented on SOLR-11508:

bq. ... keep code R/O ...

It's not enough to keep code R/O unless your situation is a predetermined static set of core
names (and not SolrCloud).  Solr writes new cores, and that means a core instance dir with

bq. ... Core discovery ...

Wether core discovery stays or leaves, I see that as immaterial.  Cores need to live _somewhere_
and Solr puts them in a configurable coreRootDirectory.  Notice it doesn't have the word "discovery"
in it.

RE Docker: I already explained that a custom SOLR_DATA_HOME (to e.g. a volume) doesn't solve
the docker/volume problem since Solr (in either mode) will write to the coreRootDirectory
which is not in SOLR_DATA_HOME.

> should be stored $$
> -----------------------------------------------------------
>                 Key: SOLR-11508
>                 URL:
>             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
(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 {{$\{}/$\{}/index/...}}, is stored in {{$\{solr.solr.home}/$\{}/}}.
> 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.
> 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,
with the rest of the data it describes.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message