[
https://issues.apache.org/jira/browse/SOLR-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359167#comment-15359167
]
Scott Blum commented on SOLR-9273:
----------------------------------
Nice stuff. 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. That way
you maximize reuse but also allow GC when a particular version of a config set
goes unused. This would allow cores to continue to reload individually instead
of having to reload by shared configset. (It would also allow cores with the
same content hash to share even if the config sets are copies of each other --
not sure if this is desirable or not.)
> Share and reuse config set in a node
> ------------------------------------
>
> Key: SOLR-9273
> URL: https://issues.apache.org/jira/browse/SOLR-9273
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
