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

Inna Balasanyan commented on MAPREDUCE-2015:
--------------------------------------------

Hello
This is the command line used 
bin/hadoop -classpath $JAR_CLASSPATH org.apache.hadoop.mapred.gridmix.Gridmix 
-Dgridmix.min.file.size=1 
-Dgridmix.output.directory=hdfs://localhost:54310/user/hduser/outgrid -generate 
1m hdfs://localhost:54310/user/hduser/outgrid 
hdfs://localhost:54310/user/hduser/rumen_output/job-trace.json

And this is the output

12/07/25 10:47:27 INFO gridmix.JobMonitor:  Job submission failed notify if 
anyone is waiting org.apache.hadoop.mapreduce.Job@fd918a
12/07/25 10:47:37 INFO mapred.JobClient: Cleaning up the staging area 
file:/tmp/hadoop-hduser/mapred/staging/hduser-78719438/.staging/job_local_0002
12/07/25 10:47:37 ERROR security.UserGroupInformation: 
PriviledgedActionException as:innab 
cause:org.apache.hadoop.mapred.FileAlreadyExistsException: Output directory 
hdfs://localhost:54310/user/hduser/outgrid already exists
12/07/25 10:47:37 ERROR gridmix.Gridmix: Startup failed
org.apache.hadoop.mapred.FileAlreadyExistsException: Output directory 
hdfs://localhost:54310/user/hduser/outgrid already exists
        at 
org.apache.hadoop.mapreduce.lib.output.FileOutputFormat.checkOutputSpecs(FileOutputFormat.java:137)
        at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:889)
        at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:850)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:396)
        at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1093)
        at 
org.apache.hadoop.mapred.JobClient.submitJobInternal(JobClient.java:850)
        at org.apache.hadoop.mapreduce.Job.submit(Job.java:500)
        at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:530)
        at 
org.apache.hadoop.mapred.gridmix.Gridmix.writeInputData(Gridmix.java:118)
        at org.apache.hadoop.mapred.gridmix.Gridmix.start(Gridmix.java:283)
        at org.apache.hadoop.mapred.gridmix.Gridmix.runJob(Gridmix.java:263)
        at org.apache.hadoop.mapred.gridmix.Gridmix.access$000(Gridmix.java:55)
        at org.apache.hadoop.mapred.gridmix.Gridmix$1.run(Gridmix.java:217)
        at org.apache.hadoop.mapred.gridmix.Gridmix$1.run(Gridmix.java:215)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:396)
        at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1093)
        at org.apache.hadoop.mapred.gridmix.Gridmix.run(Gridmix.java:215)
        at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
        at org.apache.hadoop.mapred.gridmix.Gridmix.main(Gridmix.java:390)
12/07/25 10:47:37 INFO gridmix.Gridmix: Exiting...

Thanks



                
> GridMix always throws an FileAlreadyExistsException even ouput directory is 
> not available in HDFS.
> --------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2015
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2015
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/gridmix
>    Affects Versions: 0.20.1
>            Reporter: Vinay Kumar Thota
>            Assignee: Ranjit Mathew
>
> Gridmix always throws an FileAlreadyExistsException even ouput directory is 
> not available in HDFS. Actually I was launching the Gridmix in a command line 
> for generating the data, before launching I just make sure the output 
> directory is not available in the HDFS by deleting the folder if already 
> exists.However, I could see output directory already exists exception every 
> time. Please see the attached logs for more information.

--
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

        

Reply via email to