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

Hudson commented on HDFS-4643:
------------------------------

Integrated in Hadoop-Hdfs-trunk #1368 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1368/])
    HDFS-4643. Fix flakiness in TestQuorumJournalManager. Contributed by Todd 
Lipcon. (Revision 1466253)

     Result = FAILURE
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1466253
Files : 
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/test/GenericTestUtils.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/qjournal/client/TestQuorumJournalManager.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestCheckpoint.java

                
> Fix flakiness in TestQuorumJournalManager
> -----------------------------------------
>
>                 Key: HDFS-4643
>                 URL: https://issues.apache.org/jira/browse/HDFS-4643
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: qjm, test
>    Affects Versions: 3.0.0, 2.0.3-alpha
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Trivial
>             Fix For: 3.0.0, 2.0.5-beta
>
>         Attachments: hdfs-4643.txt, hdfs-4643.txt, hdfs-4643.txt
>
>
> TestQuorumJournalManager can occasionally fail if two consecutive test cases 
> pick the same port number for the JournalNodes. In this case, sometimes an 
> IPC client can be cached from a previous test case, and then fail when it 
> tries to make an IPC over that cached connection to the now-broken 
> connection. We need to more carefully call close() on all the QJMs to prevent 
> this.

--
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

Reply via email to