lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Commented] (SOLR-9273) Share and reuse config set in a node
Date Sat, 02 Jul 2016 19:35:11 GMT


David Smiley commented on SOLR-9273:

bq. One random idea: we could content-hash the ConfigSets based on schema and solrconfig,
so the same schema+solrconfig would produce a consistent hash, which could then be a key into
a weak map for that config set.

+1 !

bq. I would like if we could move the config overlay out of the SolrConfig/ConfigSet, it should
belong to the collection and not to the configset.

But isn't the overlay fundamentally part of the configuration -- it's just an alternate way
of configuring things outside of the solrconfig.xml file?  Or maybe I misunderstand that.

BTW, wouldn't another conundrum in sharing configs be core specific references, like the
property?  I suppose this all may be cleared up if we go with Scott's idea of generating a
hash of the entire runtime hash of everything, which will mean that we don't need to do anything
special for; if you configure something with such a reference, the config will
get a different hash.

> Share and reuse config set in a node
> ------------------------------------
>                 Key: SOLR-9273
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: config-api, Schema and Analysis, SolrCloud
>            Reporter: Shalin Shekhar Mangar
>             Fix For: 6.2, master (7.0)
> Currently, each core in a node ends up creating a completely new instance of ConfigSet
with its own schema, solrconfig and other properties. This is wasteful when you have a lot
of replicas in the same node with many of them referring to the same config set in Zookeeper.
> There are many issues that need to be addressed for this to work so this is a parent
issue to track the work.

This message was sent by Atlassian JIRA

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

View raw message