hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10270) TestJMXGet:testNameNode() fails
Date Wed, 13 Apr 2016 16:17:25 GMT

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

Kihwal Lee commented on HDFS-10270:

bq. In addition playing with timeouts makes a JUnit test more complicated than a JUnit test
should be. What is you opinion about these?
Totally agree, but in reality hadoop unit tests are riddled with unreliable timeouts. Many
of them are not really unit tests.  They exist because of many reasons including Inherent
difficulties in unit testing distributed functionalities, test unfriendly designs and simply
bad test designs.  Many are aware of the issue.

> TestJMXGet:testNameNode() fails
> -------------------------------
>                 Key: HDFS-10270
>                 URL: https://issues.apache.org/jira/browse/HDFS-10270
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 3.0.0, 2.8.0
>            Reporter: Andras Bokor
>            Assignee: Gergely Novák
>            Priority: Minor
>         Attachments: HDFS-10270.001.patch, TestJMXGet.log, TestJMXGetFails.log
> It fails with java.util.concurrent.TimeoutException. Actually the problem here is that
we expect 2 as NumOpenConnections metric but it is only 1. So the test waits 60 sec then fails.
> Please find maven output so the stack trace attached ([^TestJMXGetFails.log]).

This message was sent by Atlassian JIRA

View raw message