[ 
https://issues.apache.org/jira/browse/HADOOP-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552115
 ] 

Hadoop QA commented on HADOOP-2228:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12371143/HADOOP-2228-v1.patch
against trunk revision r604440.

    @author +1.  The patch does not contain any @author tags.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests +1.  The patch passed contrib unit tests.

Test results: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1355/testReport/
Findbugs warnings: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1355/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1355/artifact/trunk/build/test/checkstyle-errors.html
Console output: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1355/console

This message is automatically generated.

> Jobs fail because job.xml exists
> --------------------------------
>
>                 Key: HADOOP-2228
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2228
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.3
>         Environment: 35 node cluster, linux
>            Reporter: Johan Oskarsson
>            Assignee: Johan Oskarsson
>             Fix For: 0.15.2, 0.16.0
>
>         Attachments: HADOOP-2228-v1.patch
>
>
> org.apache.hadoop.ipc.RemoteException: java.io.IOException: Target 
> /var/storage/4/mapred/local/jobTracker/job_200711081903_3976.xml already 
> exists
>         at org.apache.hadoop.fs.FileUtil.checkDest(FileUtil.java:271)
>         at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:117)
>         at 
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:803)
>         at 
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:784)
>         at 
> org.apache.hadoop.mapred.JobInProgress.<init>(JobInProgress.java:134)
>         at org.apache.hadoop.mapred.JobTracker.submitJob(JobTracker.java:1479)
>         at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:340)
>         at org.apache.hadoop.ipc.Server$Handler.run(Server.java:566)
>         at org.apache.hadoop.ipc.Client.call(Client.java:470)
>         at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:165)
>         at $Proxy1.submitJob(Unknown Source)
>         at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:82)
>         at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:59)
>         at $Proxy1.submitJob(Unknown Source)
>         at org.apache.hadoop.mapred.JobClient.submitJob(JobClient.java:397)
>         at org.apache.hadoop.mapred.jobcontrol.Job.submit(Job.java:345)
>         at 
> org.apache.hadoop.mapred.jobcontrol.JobControl.startReadyJobs(JobControl.java:250)
>         at 
> org.apache.hadoop.mapred.jobcontrol.JobControl.run(JobControl.java:282)
>         at java.lang.Thread.run(Thread.java:619)
> Perhaps related to HADOOP-1057, HADOOP-891 or to the rpc retry. It seems my 
> job was submitted and actually finished despite the exception. Could it be 
> that the job went in and the rpc retry decided to submit it again anyway?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to