[
https://issues.apache.org/jira/browse/SOLR-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363864#comment-15363864
]
Noble Paul commented on SOLR-9273:
----------------------------------
bq. so I do wonder at the effects on Zookeeper/event notification to the
clients.
Today , we read the whole content of all config files on every core load from
ZK. Which is over and above the regular state updates. So, there will be a big
reduction in the data read from ZK.
bq.So would this mean that there's one way of loading solrconfig in stand-alone
and one for SolrCloud?
We already do it. The ConfigSetService have multiple implementations for cloud
& non-cloud. So, it would be opaque to the API caller, what kind of ConfigSet
it is getting
> 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]
