lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Heiden <markus.hei...@s24.com>
Subject Re: SolrCloud collection properties
Date Wed, 06 May 2015 08:43:22 GMT
We are currently having many custom properties defined in the
core.properties which are used in our solrconfig.xml, e.g.
         <str name="enabled">${solr.enable.cachewarming:true}</str>

Now we want to migrate to SolrCloud and want to define these properties for
a collection. But defining properties when creating a collection just
writes them into the core.properties of the created cores. This is a pain,
because we have a lot of properties and you have to specify each as an URL
parameter. Furthermore it seems that these properties are not propagated to
the cores for new shards, if you e.g. split a shard -> error-prone.

As you already mentioned, we could resolve this properties ourselves by
using many configsets instead of just one. My question was, if it is
possible to use just one configset in this case and specify collection
specific properties at the collection level? This seems for me the better
way to handle the configuration complexity.

Markus

2015-05-06 3:48 GMT+02:00 Erick Erickson <erickerickson@gmail.com>:

> _What_ properties? Details matter....
>
> And how do you do this now? Assuming you do this with separate conf
> directories, these are then just configsets in Zookeeper and you can
> have as many of them as you want. Problem here is that each one of
> them is a complete set of schema and config files, AFAIK the config
> set is the finest granularity that you have OOB.
>
> Best,
> Erick
>
> On Tue, May 5, 2015 at 6:55 AM, Markus Heiden <markus.heiden@s24.com>
> wrote:
> > Hi,
> >
> > we are trying to migrate from Solr 4.10 to SolrCloud 4.10. I understood
> > that SolrCloud uses collections as abstraction from the cores. What I am
> > missing is a possibility to store collection-specific properties in
> > Zookeeper. Using property.foo=bar in CREATE-URLs just sets core-specific
> > properties which are not distributed, e.g. if I migrate a shard from one
> > node to another.
> >
> > How do I define collection-specific properties (to be used in
> > solrconfig.xml and schema.xml) which get distributed with the collection
> to
> > all nodes?
> >
> > Why do I try that? Currently we have different cores which structure is
> > identical, but have each having some specific properties. I would like to
> > have a single configuration for them in Zookeeper from which I want to
> > create different collections, which just differ in the value of some
> > properties.
> >
> > Markus
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message