hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10962) TestRequestHedgingProxyProvider is flaky
Date Wed, 05 Oct 2016 22:21:20 GMT

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

Hudson commented on HDFS-10962:
-------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10549 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/10549/])
HDFS-10962. TestRequestHedgingProxyProvider is flaky. (wang: rev e68c7b96c76b243da53ae539e7c760bf2c08f26e)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/RequestHedgingProxyProvider.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestRequestHedgingProxyProvider.java


> TestRequestHedgingProxyProvider is flaky
> ----------------------------------------
>
>                 Key: HDFS-10962
>                 URL: https://issues.apache.org/jira/browse/HDFS-10962
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.6.4
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>             Fix For: 2.8.0, 3.0.0-alpha2
>
>         Attachments: HDFS-10962.001.patch, HDFS-10962.002.patch
>
>
> This test fails occasionally with an error like this:
> {noformat}
> org.apache.hadoop.hdfs.server.namenode.ha.TestRequestHedgingProxyProvider.testHedgingWhenOneFails
> Error Message
> Wanted but not invoked:
> namenodeProtocols.getStats();
> -> at org.apache.hadoop.hdfs.server.namenode.ha.TestRequestHedgingProxyProvider.testHedgingWhenOneFails(TestRequestHedgingProxyProvider.java:78)
> Actually, there were zero interactions with this mock.
> Stacktrace
> org.mockito.exceptions.verification.WantedButNotInvoked: 
> Wanted but not invoked:
> namenodeProtocols.getStats();
> -> at org.apache.hadoop.hdfs.server.namenode.ha.TestRequestHedgingProxyProvider.testHedgingWhenOneFails(TestRequestHedgingProxyProvider.java:78)
> Actually, there were zero interactions with this mock.
> 	at org.apache.hadoop.hdfs.server.namenode.ha.TestRequestHedgingProxyProvider.testHedgingWhenOneFails(TestRequestHedgingProxyProvider.java:78)
> Standard Output
> 2016-09-26 15:26:02,234 WARN  hdfs.DFSUtil (DFSUtil.java:getAddressesForNameserviceId(689))
- Namenode for mycluster-26780990 remains unresolved for ID nn1.  Check your hdfs-site.xml
file to ensure namenodes are configured properly.
> 2016-09-26 15:26:02,340 WARN  hdfs.DFSUtil (DFSUtil.java:getAddressesForNameserviceId(689))
- Namenode for mycluster-26780990 remains unresolved for ID nn2.  Check your hdfs-site.xml
file to ensure namenodes are configured properly.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message