hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3554) TestRaidNode is failing
Date Mon, 25 Jun 2012 14:14:43 GMT

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

Robert Joseph Evans commented on HDFS-3554:
-------------------------------------------

It looks like there is no history server up and running.  In Yarn there is a race in the client.
 If the client asks for status if the AM is still up and running then it will talk to the
AM.  If it has exited, which it tends to do when the MR job has completed then the client
will fall over to the history server.  It looks like while you are running using the minicluster
there is no corresponding history server to fulfill the request.
                
> TestRaidNode is failing
> -----------------------
>
>                 Key: HDFS-3554
>                 URL: https://issues.apache.org/jira/browse/HDFS-3554
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: contrib/raid, test
>    Affects Versions: 3.0.0
>            Reporter: Jason Lowe
>            Assignee: Weiyan Wang
>
> After MAPREDUCE-3868 re-enabled raid, TestRaidNode has been failing in Jenkins builds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message