[
https://issues.apache.org/jira/browse/SOLR-12386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17100807#comment-17100807
]
David Smiley commented on SOLR-12386:
-------------------------------------
For the case of an incomplete configSet (i.e. one that didn't exist and is in
the process of coming into existence), I think the solution is somewhat simple:
SOLR-14446 (Use Zk.multi when uploading configSets) in combination with a
retry mechanism on creation of ZkSolrResourceLoader that ensures the ZK based
configSet dir exists. That retry mechanism would probably do a Zk.sync()
in-between. Not sure if that retry strategy should go in SOLR-14446 or be
another issue.
A separate issue(s) is more comprehensively thinking about how to deal with
_modifications_ to a configSet – e.g. for schema mutations, or otherwise. That
would probably involve a Zk.sync as well but with as yet unspecified means to
ensure we don't call it too often.
> Test fails for "Can't find resource" for files in the _default configset
> ------------------------------------------------------------------------
>
> Key: SOLR-12386
> URL: https://issues.apache.org/jira/browse/SOLR-12386
> Project: Solr
> Issue Type: Test
> Components: SolrCloud
> Reporter: David Smiley
> Priority: Minor
> Attachments: cant find resource, stacktrace.txt
>
>
> Some tests, especially ConcurrentCreateRoutedAliasTest, have failed
> sporadically failed with the message "Can't find resource" pertaining to a
> file that is in the default ConfigSet yet mysteriously can't be found. This
> happens when a collection is being created that ultimately fails for this
> reason.
--
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
