[
https://issues.apache.org/jira/browse/SOLR-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005975#comment-13005975
]
Robert Muir commented on SOLR-2422:
-----------------------------------
The first problem I found here is in testConnect, it has a timeout of 100ms
Our lucene slave is pretty busy (lots of cores, so lots of tests going on at
once in parallel).
By changing this timeout to AbstractZkTestCase.TIMEOUT (10000ms), I found the
test to be significantly more reliable. This is consistent with the other test
cases, they seem to use this timeout.
I tested this on hudson and it seems a big improvement, so I committed the
trivial change in r1080852 (sorry for the heavy-commit, I know we are all sick
of the hudson instability).
> Improve reliability of ZkSolrClientTest
> ---------------------------------------
>
> Key: SOLR-2422
> URL: https://issues.apache.org/jira/browse/SOLR-2422
> Project: Solr
> Issue Type: Bug
> Components: Build
> Affects Versions: 4.0
> Reporter: Robert Muir
>
> The ZKSolrClient test is pretty unreliable, it seems to fail a significant
> portion of the time on hudson (often on my local as well).
> Additionally it seems to somehow sometimes (maybe depending upon retry loop?)
> leave a lot of zookeeper threads running.
> I ran into these issues when i discovered that trying to interrupt() these
> threads after the test completed was triggering a JRE bug, but by working
> through it I saw how unreliable the test is.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
