You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2015/10/24 18:51:27 UTC

[jira] [Created] (SOLR-8205) Make UpdateShardHandler's thread pool configurable

Shalin Shekhar Mangar created SOLR-8205:
-------------------------------------------

             Summary: Make UpdateShardHandler's thread pool configurable
                 Key: SOLR-8205
                 URL: https://issues.apache.org/jira/browse/SOLR-8205
             Project: Solr
          Issue Type: Improvement
          Components: SolrCloud
            Reporter: Shalin Shekhar Mangar
             Fix For: 5.4, Trunk


Resource consumption under arbitrary query load can be limited with careful bound on maximumPoolSize in ShardHandlerFactory and appropriate timeouts but it is not possible to do the same for updates because of UpdateShardHandler uses an unbounded cached thread pool. This is a major problem, for example, when trying use SolrCloud as a service and attempting to guarantee SLAs.

I propose to make the UpdateShardHandler's core/max thread pool size and thread keep alive time configurable. If we change the pool size to be bounded, does it make sense to make the queue size also configurable?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org