[
https://issues.apache.org/jira/browse/SOLR-8205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816351#comment-17816351
]
David Smiley commented on SOLR-8205:
------------------------------------
{quote}A downside to configuring an upper bound will be big update reorders
(when that upper bound is hit) and then undetected shard inconsistency as a
result.
{quote}
I don't understand. Can someone clarify? _(I have no agenda of doing this
issue.)_
> 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
> Priority: Major
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
