[ 
https://issues.apache.org/jira/browse/SOLR-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580077#comment-13580077
 ] 

Steve Rowe commented on SOLR-4454:
----------------------------------

I updated my trunk checkout to after the last of several of Mark Miller's Solr 
test improvements ([http://svn.apache.org/viewvc?view=rev&rev=1446981]) and 
then ran ChaosMonkeySafeLeaderTest.testDistribSearch five times - all five 
passed.  (I [mentioned on 
SOLR-4462|https://issues.apache.org/jira/browse/SOLR-4462?focusedCommentId=13579360&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13579360]
 that this test had previously failed four out of five times for me.)

If others see the same improvement, this issue can be resolved as fixed.
                
> non-reproducible long "stall" running 
> ChaosMonkeySafeLeaderTest.testDistribSearch
> ---------------------------------------------------------------------------------
>
>                 Key: SOLR-4454
>                 URL: https://issues.apache.org/jira/browse/SOLR-4454
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>            Assignee: Mark Miller
>         Attachments: threaddump.0.txt, threaddump.1.txt, threaddump.2.txt, 
> threaddump.3.txt, threaddump.4.txt, threaddump.5.txt, threaddump.6.txt
>
>
> while testing out my patch for SOLR-4451, i saw an extremely long "stalled" 
> case of ChaosMonkeySafeLeaderTest.testDistribSearch that i couldn't reproduce
> i took a couple of thread dumps, but nothing jumped out at me, other then 
> that one thread is sleeping as part of 
> AbstractDistribZkTestBase.waitForRecoveriesToFinish

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]

Reply via email to