[
https://issues.apache.org/jira/browse/SOLR-13579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072035#comment-17072035
]
Andrzej Bialecki commented on SOLR-13579:
-----------------------------------------
As explained above, in theory CoreContainer-level components could be managed
by the framework but it would require adding quite a bit of scaffolding so the
framework knows how to manage a particular "type" of component - and all this
just to manage a single instance... so it wouldn't make much sense, it's best
to use it for situations where there are multiple components competing to use
limited resources.
OTOH, the {{ConcurrentMergeScheduler}} is a perfect candidate for using this
API, because it's instantiated at an IndexWriter level, there are multiple
instances of it across the cores, and they all compete for CPU and IO. This is
one of the use cases described in the SIP-4.
> Create resource management API
> ------------------------------
>
> Key: SOLR-13579
> URL: https://issues.apache.org/jira/browse/SOLR-13579
> Project: Solr
> Issue Type: New Feature
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Attachments: SOLR-13579.patch, SOLR-13579.patch, SOLR-13579.patch,
> SOLR-13579.patch, SOLR-13579.patch, SOLR-13579.patch, SOLR-13579.patch,
> SOLR-13579.patch, SOLR-13579.patch, SOLR-13579.patch
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> Resource management framework API supporting the goals outlined in SOLR-13578.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
