[
https://issues.apache.org/jira/browse/SOLR-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859720#comment-13859720
]
Kranti Parisa commented on SOLR-3197:
-------------------------------------
I like the idea of having a configurable option, say
<warmupThreads>1</warmupThreads>
so that user can change the number based on their needs.
Neil, to your point "When Solr is configured not to serve queries while
warming" how can we do this when the instance is in a cluster under load
balancer?
> Allow firstSearcher and newSearcher listeners to run in multiple threads
> ------------------------------------------------------------------------
>
> Key: SOLR-3197
> URL: https://issues.apache.org/jira/browse/SOLR-3197
> Project: Solr
> Issue Type: Improvement
> Reporter: Lance Norskog
>
> SolrCore submits all listeners (firstSearcher and newSearcher) to a java
> ExecutorService, but uses a single-threaded one.
> line 965 in the trunk:
> {code}
> SolrCore.java around line 965: final ExecutorService searcherExecutor =
> Executors.newSingleThreadExecutor();
> line 1280 in the trunk:
> SolrCore.java around line 1280 runs first the, and then the first and new
> searchers, all with the searcherExecutor object created at line 965.
> Would it work if we changed this ExecutorService to a thread pool version?
> This seems like it should work:
> {code}
> java.util.concurrent.Executors.newFixedThreadPool(int nThreads, ThreadFactory
> threadFactory);
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
