Hadoop 2.2.0: Cannot run PI in under YARN
When I tried the PI example, I got File does not exist error. The mapreduce frame work is set to yarn. Any idea what's wrong? .Failing this attempt.. Failing the application. 13/11/07 18:13:02 INFO mapreduce.Job: Counters: 0 Job Finished in 104.852 seconds java.io.FileNotFoundException: File does not exist: hdfs://10.1.1.1:9000/user/hdfs/QuasiMonteCarlo_1383869474575_815496929/out/reduce-out at org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1110) at org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1102) at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81) at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1102) at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1749) at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1773) at org.apache.hadoop.examples.QuasiMonteCarlo.estimatePi(QuasiMonteCarlo.java:314) at org.apache.hadoop.examples.QuasiMonteCarlo.run(QuasiMonteCarlo.java:354) at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) at org.apache.hadoop.examples.QuasiMonteCarlo.main(QuasiMonteCarlo.java:363) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:72) at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144) at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.util.RunJar.main(RunJar.java:212)
Re: Hadoop 2.2.0: Cannot run PI in under YARN
This is just a symptom not the root cause. Please check the YARN web UI at 8088 on ResourceManager machine and browse to the application page. It should give you more details. Thanks, +Vinod On Nov 8, 2013, at 8:57 AM, Ping Luo wrote: java.io.FileNotFoundException: File does not exist -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: Hadoop 2.2.0: Cannot run PI in under YARN
The problem is resolved. The resource manager address was not configured correctly. Thanks, Ping From: Vinod Kumar Vavilapalli vino...@hortonworks.com To: user@hadoop.apache.org; Ping Luo luop0...@yahoo.com Sent: Friday, November 8, 2013 1:26 PM Subject: Re: Hadoop 2.2.0: Cannot run PI in under YARN This is just a symptom not the root cause. Please check the YARN web UI at 8088 on ResourceManager machine and browse to the application page. It should give you more details. Thanks, +Vinod On Nov 8, 2013, at 8:57 AM, Ping Luo wrote: java.io.FileNotFoundException: File does not exist CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
