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

Anbang Hu commented on HDFS-13563:
----------------------------------

[~elgoiri], there are 4 timeout tests in this test class, but they are not the 
reason for the other 32 failures. It is the restarting NN1 with -upgrade option 
in testUpgradeCommand that did not release the journalnode directory. I opened 
[HDFS-13630|https://issues.apache.org/jira/browse/HDFS-13630] for discussion.

In addition, I would vote for having randomized MiniDFSCluster base path for 
this test class. But we should leave 
[HDFS-13630|https://issues.apache.org/jira/browse/HDFS-13630] open until root 
cause is found.

> TestDFSAdminWithHA times out on Windows
> ---------------------------------------
>
>                 Key: HDFS-13563
>                 URL: https://issues.apache.org/jira/browse/HDFS-13563
>             Project: Hadoop HDFS
>          Issue Type: Test
>            Reporter: Anbang Hu
>            Assignee: Anbang Hu
>            Priority: Minor
>              Labels: Windows
>         Attachments: HDFS-13563.000.patch, HDFS-13563.001.patch
>
>
> {color:#333333}[Daily Windows 
> build|https://builds.apache.org/job/hadoop-trunk-win/467/testReport/] shows 
> TestDFSAdminWithHA has 4 timeout tests with "{color}test timed out after 
> 30000 milliseconds{color:#333333}"{color}
> {code:java}
> org.apache.hadoop.hdfs.tools.TestDFSAdminWithHA.testRefreshUserToGroupsMappingsNN1DownNN2Down
> org.apache.hadoop.hdfs.tools.TestDFSAdminWithHA.testRefreshServiceAclNN1DownNN2Down
> org.apache.hadoop.hdfs.tools.TestDFSAdminWithHA.testRefreshCallQueueNN1DownNN2Down
> org.apache.hadoop.hdfs.tools.TestDFSAdminWithHA.testRefreshSuperUserGroupsConfigurationNN1DownNN2Down
> {code}
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to