[
https://issues.apache.org/jira/browse/SOLR-12590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16560124#comment-16560124
]
Steve Rowe commented on SOLR-12590:
-----------------------------------
{quote}
bq. Under SolrCloud, resources to be loaded are first looked up in ZooKeeper
under the collection's configset znode. If the resource isn't found there, Solr
will fall back to loading resources from the filesystem.
A nicely concise and clear lead paragraph, I like it. Side question: was this
fallback logic 'always' there (and I just didn't know about it, oops) or is it
something introduced in a recent-ish version?
{quote}
I think it's always been there. The comment below (positioned after failing to
load a resource from ZooKeeper), dates to 2010, when SolrCloud was committed to
Subversion trunk (SOLR-1873):
{code:java|title=ZkZolrResourceLoader.openResource() (branch_7x)}
121: try {
122: // delegate to the class loader (looking into $INSTANCE_DIR/lib jars)
123: is =
classLoader.getResourceAsStream(resource.replace(File.separatorChar, '/'));
{code}
bq. So yes, if the wrapper model concept is not or no longer needed then let's
not mention it in the documentation.
Do you have the bandwidth to test this assertion? I'd rather not remove docs
unless we can verify the alternative.
> Improve Solr resource loader coverage in the ref guide
> ------------------------------------------------------
>
> Key: SOLR-12590
> URL: https://issues.apache.org/jira/browse/SOLR-12590
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Steve Rowe
> Assignee: Steve Rowe
> Priority: Major
> Attachments: SOLR-12590.patch
>
>
> In SolrCloud, storing large resources (e.g. binary machine learned models) on
> the local filesystem should be a viable alternative to increasing ZooKeeper's
> max file size limit (1MB), but there are undocumented complications.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
