[
https://issues.apache.org/jira/browse/SOLR-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917278#comment-13917278
]
Mark Miller commented on SOLR-5714:
-----------------------------------
bq. Why not just make the implicit default (if not present in config)
contingent on the luceneMatchVersion? if < 4.7, default=false; else
default=true ?
On further thought, I'm not sure I prefer that. It's kind of a special case -
the global cache is created with the settings for the first directoryFactory
that is created. It seems more normal for this to be per instance by default,
and so I still kind of think it's best to default it to on, but require it to
be there explicitly for that. It feels right that if you take it away, the
configuration would apply per instance.
And then clean it up eventually by allowing it to be configured via solr.xml or
something.
> You should be able to use one pool of memory for multiple collection's HDFS
> block caches.
> -----------------------------------------------------------------------------------------
>
> Key: SOLR-5714
> URL: https://issues.apache.org/jira/browse/SOLR-5714
> Project: Solr
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 4.7, 5.0
>
> Attachments: SOLR-5714.patch
>
>
> Currently, you have to specify how much direct memory to allocate per
> SolrCore. This can be inefficient, and has some negative consequences - for
> instance, when replicating, many times two HDFS directories will exist for
> the same index briefly, which will double the RAM used for that SolrCore.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
