[
https://issues.apache.org/jira/browse/MAPREDUCE-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980323#comment-13980323
]
Hadoop QA commented on MAPREDUCE-5749:
--------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12641799/MAPREDUCE-5749v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4555//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4555//console
This message is automatically generated.
> TestRMContainerAllocator#testReportedAppProgress Failed
> -------------------------------------------------------
>
> Key: MAPREDUCE-5749
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5749
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: shenhong
> Assignee: Jason Lowe
> Attachments: MAPREDUCE-5749.patch, MAPREDUCE-5749v2.patch,
> TestRMContainerAllocator_failure.txt
>
>
> When execute "mvn test
> -Dtest=TestRMContainerAllocator#testReportedAppProgress", It failed with
> message:
> {code}
> Caused by: java.io.FileNotFoundException: File
> /home/yuling.sh/hadoop-common/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/target/org.apache.hadoop.mapreduce.v2.app.TestRMContainerAllocator/appattempt_1392009213299_0001_000001/.staging/job_1392009213299_0001/job.xml
> does not exist
> {code}
> But in fact, the job.xml exits:
> {code}
> -rw-rw-r-- 1 yuling.sh yuling.sh 65791 2月 10 13:13
> /home/yuling.sh/hadoop-common/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/target/org.apache.hadoop.mapreduce.v2.app.TestRMContainerAllocator/yuling.sh/.staging/job_1392009213299_0001/job.xml
> {code}
> See the following code:
> {code}
> public Job submit(Configuration conf, boolean mapSpeculative,
> boolean reduceSpeculative) throws Exception {
> String user = conf.get(MRJobConfig.USER_NAME, UserGroupInformation
> .getCurrentUser().getShortUserName());
> conf.set(MRJobConfig.USER_NAME, user);
> conf.set(MRJobConfig.MR_AM_STAGING_DIR, testAbsPath.toString());
> conf.setBoolean(MRJobConfig.MR_AM_CREATE_JH_INTERMEDIATE_BASE_DIR, true);
> // TODO: fix the bug where the speculator gets events with
> // not-fully-constructed objects. For now, disable speculative exec
> conf.setBoolean(MRJobConfig.MAP_SPECULATIVE, mapSpeculative);
> conf.setBoolean(MRJobConfig.REDUCE_SPECULATIVE, reduceSpeculative);
> init(conf);
> start();
> DefaultMetricsSystem.shutdown();
> Job job = getContext().getAllJobs().values().iterator().next();
> if (assignedQueue != null) {
> job.setQueueName(assignedQueue);
> }
> // Write job.xml
> String jobFile = MRApps.getJobFile(conf, user,
> TypeConverter.fromYarn(job.getID()));
> LOG.info("Writing job conf to " + jobFile);
> new File(jobFile).getParentFile().mkdirs();
> conf.writeXml(new FileOutputStream(jobFile));
> return job;
> }
> {code}
> At first, user is "yuling.sh", but the UGI is setted to attemptId at
> "start();", after that, job.xml write to
> yuling.sh/.staging/job_1392009213299_0001/job.xml. But when the job is
> running, MRAppMaster can't find the job.xml at
> appattempt_1392009213299_0001_000001/.staging/job_1392009213299_0001.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
