You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Robert Joseph Evans (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/29 16:30:26 UTC
[jira] [Resolved] (MAPREDUCE-4080) FileNotFoundException while
accessing job configuration from UI.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Joseph Evans resolved MAPREDUCE-4080.
--------------------------------------------
Resolution: Duplicate
I saw this same issue while working on MAPREDUCE-3972, and I fixed it as part of that JIRA. I did this because I considered it a threading issue. The move from done_intermediate to done was not coordinated with the reading of the Configuration file. It also was not coordinated with reading the jhist file or many other things.
> FileNotFoundException while accessing job configuration from UI.
> ----------------------------------------------------------------
>
> Key: MAPREDUCE-4080
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4080
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver, mrv2
> Affects Versions: 2.0.0, trunk
> Reporter: Bhallamudi Venkata Siva Kamesh
> Priority: Critical
>
> Tried to access the job configuration from UI, when the job history files were still in the intermediate directory. JHS displayed the configurations of the job. Again tried to access the configurations of the same job, when the job history files were in the done directory. This time got the following exception
> {noformat}
> java.io.FileNotFoundException: File does not exist: /jobhistory/intermediate/kamesh/job_1332999698561_0005_conf.xml
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getBlockLocationsUpdateTimes(FSNamesystem.java:1153)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getBlockLocations(FSNamesystem.java:1115)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getBlockLocations(FSNamesystem.java:1087)
> {noformat}
--
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