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

Hudson commented on HBASE-4746:
-------------------------------

Integrated in HBase-0.92 #118 (See 
[https://builds.apache.org/job/HBase-0.92/118/])
    HBASE-4746  Fix TestRegionServerCoprocessorExceptionWithXXX (Mikhail Bautin)

tedyu : 
Files : 
* /hbase/branches/0.92/CHANGES.txt
* 
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/coprocessor/TestRegionServerCoprocessorExceptionWithAbort.java
* 
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/coprocessor/TestRegionServerCoprocessorExceptionWithRemove.java

                
> Use a random ZK client port in unit tests so we can run them in parallel
> ------------------------------------------------------------------------
>
>                 Key: HBASE-4746
>                 URL: https://issues.apache.org/jira/browse/HBASE-4746
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Mikhail Bautin
>            Assignee: Mikhail Bautin
>             Fix For: 0.94.0
>
>         Attachments: 4746-trunk-v2.txt, D255.1.patch, D255.2.patch, 
> D279-trunk-v5.txt, D279-trunk-v7.txt, D279.1.patch, D279.2.patch, 
> D279.3.patch, D279.4.patch, D279.5.patch, D279.6.patch, D279.7.patch, D279.92
>
>
> The hard-coded ZK client port has long been a problem for running HBase test 
> suite in parallel. The mini ZK cluster should run on a random free port, and 
> that port should be passed to all parts of the unit tests that need to talk 
> to the mini cluster. In fact, randomizing the port exposes a lot of places in 
> the code where a new configuration is instantiated, and as a result the 
> client tries to talk to the default ZK client port and times out.
> The initial fix is for 0.89-fb, where it already allows to run unit tests in 
> parallel in 10 minutes. A fix for the trunk will follow.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to