[
https://issues.apache.org/jira/browse/SOLR-8772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177838#comment-15177838
]
Gus Heck commented on SOLR-8772:
--------------------------------
If you mean something like ResourceLoaderAware from my earlier patches which
merely added another line here in SolrCore.java:
{code}
// Finally tell anyone who wants to know
resourceLoader.inform(resourceLoader);
resourceLoader.inform(this); // last call before the latch is released.
} catch (Throwable e) {
{code}
That's fine, but if you mean to let the core call
{code}
} finally {
// allow firstSearcher events to fire and make sure it is released
latch.countDown();
}
{code}
before the processed blob is available that's a problem for the use case that
motivated this and for pretty much any use case that relies on that component
to provide an accurate search result.
> 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: Sub-task
> 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]
