[
https://issues.apache.org/jira/browse/SOLR-12386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488082#comment-16488082
]
Hoss Man commented on SOLR-12386:
---------------------------------
This overall symptom sounds really familar – see SOLR-12021.
I wonder if the root cause here is similar to what I found in that jira?
{quote}[resource files] are being loaded with
{{...getClassLoader().getResourceAsStream(resourceName)}} – but nothing is ever
closing the stream, so it can eventually (depending on what test classes run in
each JVM and how many files they try to open like this) cause the JVM to hit
the ulimit for open file handles – but that specific cause of the failure is
never reported, because {{ClassLoader.getResourseAsStream(...)}} is explicity
designed to swallow any IOExceptions encountered and just returns "null"...
{quote}
...allthough there was definitely some leaked InputStreams in that jira, there
wouldn't neccessarily even have to be a resource leak to see similar problems:
if individual tests are opening a lot of cores concurrently, they could be
hitting the ulimit on jenkins ("randomly" depending on what other tests were
run in the same JVM causing a variable number of open file handles to various
class files held open by the current system classloader) but instead of
throwing a clean error to that effect getSourceAsStream just returns null and
causes the SolrResourceLoader to assume it doesn't exist ... maybe?
(we should probably consider making {{ClassLoader.getResourceAsStream}} a
forbidden API to prevent this risk even if it's *not* the cause of the current
failures.)
> 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
> Security Level: Public(Default Security Level. Issues are Public)
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
