[
https://issues.apache.org/jira/browse/SOLR-12386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383703#comment-17383703
]
Mark Robert Miller commented on SOLR-12386:
-------------------------------------------
Two comments:
* in combination with a retry mechanism on creation of ZkSolrResourceLoader
that ensures the ZK based configSet dir exists.
Retries and attempts from everyone to create core zk nodes (and retry, often
per path part) is bad scalable silly behavior. You can save a lot of craziness
by simple having a single node on first startup create all the fundamental and
expected zk nodes.
* That retry mechanism would probably do a Zk.sync() in-between.
Careful about over use of that sync - it's called a "slow read" and it's easy
to over use without need. It's also not likely needed in these cases where you
should likely be doing optimistic actions that will fail if another client is
racing you regardless of if you sync all over.
> 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...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
