[
https://issues.apache.org/jira/browse/SOLR-16547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634086#comment-17634086
]
Noble Paul commented on SOLR-16547:
-----------------------------------
{quote}Can you give another example where sharing some state would cause users
to see different behavior? {quote}
Ideally it shouldn't. But, we may not be able to support every single feature
when the actual objects are shared. for instance, we have a different
classloader for each core today. When objects are shared, that is not possible.
But, for a power user who is more concerned about resource usage may not want
different classloaders for each core
> Share and reuse all possible Objects between cores
> --------------------------------------------------
>
> Key: SOLR-16547
> URL: https://issues.apache.org/jira/browse/SOLR-16547
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Priority: Major
>
> The objective is to minimize the heap usage where nodes host very large
> number of cores.
> A very common usecase is where all (or a lot of cores ) in a node uses the
> same configset. . We will make this an opt-in feature so that a common user
> wouldn't see a different behaviour.
> To enable this feature, add the following flag to {{solrconfig.xml}}
> {{<shareCoreData>true</shareCoreData>}}
>
> I shall open sub-tickets to enable sharing of specific objects
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
