[
https://issues.apache.org/jira/browse/HDFS-10270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235349#comment-15235349
]
Kihwal Lee commented on HDFS-10270:
-----------------------------------
It looks like a race was introduced after the jmx caching was "fixed". Certain
metrics values in JMX is now using the cached value, which expires in 10
seconds by default. Since the ipc client idle timeout is also 10 seconds, The
ipc connection may get closed before the jmx refresh. So the number of actual
connections reaches to 2, but can drop to 1 just before a new jmx data is
fetched. We could fix this by either lowering the jmx cache expiration or
increasing ipc client idle timeout. Since it is a JMX test, it might be better
to leave the jmx setting as default and change the ipc timeout to, say, 15
seconds.
> 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)
