[
https://issues.apache.org/jira/browse/SOLR-11581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16233891#comment-16233891
]
Michael McCandless commented on SOLR-11581:
-------------------------------------------
{{NoMergeScheduler}} is designed to be a singleton class -- its ctor is private
because you are supposed to simply use its static {{INSTANCE}} value. Can we
modify Solr's merge scheduler parsing code to just use the singleton?
Also, it's not a good idea to defer all merging until the end: Lucene will at
that point (when you finally turn on merging) have to do all the merges it
would have been doing all along, so you're not saving any work overall.
But increasing IW's RAM buffer, and using fewer threads (it's diminishing
returns on indexing throughput as you increase thread count), will decrease the
merge pressure.
> NoMergeScheduler ctor should be public for allowing instantiation from SOLR
> ---------------------------------------------------------------------------
>
> Key: SOLR-11581
> URL: https://issues.apache.org/jira/browse/SOLR-11581
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Nawab Zada Asad iqbal
> Priority: Minor
>
> There are scenarios where a SOLR user may want to use NoMergeScheduler.
> However, it is not possible to use it today, since its constructor is private
> and solrconfig.xml requires a Scheduler with public constructor.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
