hadoop-hdfs-issues mailing list archives

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

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

Andras Bokor commented on HDFS-10270:
-------------------------------------

Hi [~kihwal],

We do not see the value to check NumOpenConnections since it can cause intermittent failures
and with the other checks the JMX metrics are tested enough. Our suggestion is to remove NumOpenConnections
check. Do you see any disadvantages removing NumOpenConnections check?

> 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
(v6.3.4#6332)

Mime
View raw message