[
https://issues.apache.org/jira/browse/HDFS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400087#comment-13400087
]
Weiyan Wang commented on HDFS-3554:
-----------------------------------
After hours of debugging, I found the reason for the failure is that JobMonitor
gets the following exception when it check the completeness of one job:
2012-06-23 19:52:18,196 ERROR [org.apache.hadoop.raid.JobMonitor@3515f1d3]
raid.JobMonitor (JobMonitor.java:doMonitor(116)) - JobMonitor exception
java.io.IOException: Job status not available
at org.apache.hadoop.mapreduce.Job.updateStatus(Job.java:315)
at org.apache.hadoop.mapreduce.Job.isComplete(Job.java:592)
at org.apache.hadoop.raid.DistRaid.checkComplete(DistRaid.java:282)
at org.apache.hadoop.raid.JobMonitor.doMonitor(JobMonitor.java:106)
at org.apache.hadoop.raid.JobMonitor.run(JobMonitor.java:61)
at java.lang.Thread.run(Thread.java:619)
But I don't know what causes this. I guess it's mapreduce bug because sometimes
I get this exception while sometimes I don't. Anyone have an idea? Thanks!
> 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
