Coincidentally, I just ran into the same exception. What's probably happening is that you're specifying some jar file in your job as an absolute local path (e.g. just "/home/koert/test-assembly-0.1-SNAPSHOT.jar"), but your Hadoop config has the default FS set to HDFS.
So your driver does not know that it should tell executors to download that file from the driver. If you specify the jar with the "file:" scheme that should solve the problem. On Thu, Jun 19, 2014 at 10:22 AM, Koert Kuipers <ko...@tresata.com> wrote: > i am trying to understand how yarn-client mode works. i am not using > Application application_1403117970283_0014 failed 2 times due to AM > Container for appattempt_1403117970283_0014_000002 exited with exitCode: > -1000 due to: File file:/home/koert/test-assembly-0.1-SNAPSHOT.jar does not > exist > .Failing this attempt.. Failing the application. -- Marcelo
