[
https://issues.apache.org/jira/browse/SOLR-8772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175005#comment-15175005
]
Shalin Shekhar Mangar commented on SOLR-8772:
---------------------------------------------
+1 to the idea.
The one difference between BlobStoreAware and the similarly named SolrCoreAware
would be that any exception thrown during SolrCoreAware.inform method aborts
the loading of the core but I assume that that wouldn't be the case with
BlobStoreAware.
I had a small chat with Noble and we came to the conclusion that in order to
get the blob store and runtime lib features usable, we need this issue,
SOLR-8751 and a few others. [~noble.paul] -- perhaps this is a good time to
open a parent issue to track all these sub-features in one place?
> components that rely on blob store should be loaded as soon as it is available
> ------------------------------------------------------------------------------
>
> Key: SOLR-8772
> URL: https://issues.apache.org/jira/browse/SOLR-8772
> Project: Solr
> Issue Type: Improvement
> Reporter: Noble Paul
> Assignee: Noble Paul
>
> If a component is set as {{runtimeLib=true}} it automatically becomes
> {{startup=lazy}} which means there is no way we can know that if the
> component could be successfully loaded till a request is made and the
> component is used. This is suboptimal behavior. The ops will have no means of
> knowing if everything is OK. Also , the first request will be unpredictably
> slow
> This means that , the server would keep checking for availability of blob
> store ( .system collection) and all components will get loaded as soon as the
> {{.system}} collection is available for querying
> Also, it will be possible for components to have an interface called
> {{BlobStoreAware}} . The component would get a callback as and when the blob
> store is available
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
