[
https://issues.apache.org/jira/browse/OOZIE-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158577#comment-16158577
]
Peter Cseh commented on OOZIE-2547:
-----------------------------------
Without the launcher logs it's hard to say anything. The proper files should be
mentioned in the --files section. However, 5.10.0 was affected by OOZIE-2802
and OOZIE-2806 which was both fixed in CDH 5.10.1. [~szhemzhitsky], can you
provide more information about your workflow? (possibly the <spark-opts> part)
please open an other jira for this though.
> Add mapreduce.job.cache.files to spark action
> ---------------------------------------------
>
> Key: OOZIE-2547
> URL: https://issues.apache.org/jira/browse/OOZIE-2547
> Project: Oozie
> Issue Type: Bug
> Reporter: Satish Subhashrao Saley
> Assignee: Satish Subhashrao Saley
> Priority: Minor
> Fix For: 4.3.0
>
> Attachments: OOZIE-2547-1.patch, OOZIE-2547-4.patch,
> OOZIE-2547-5.patch, yarn-cluster_launcher.txt
>
>
> Currently, we pass jars using --jars option while submitting spark job. Also,
> we add spark.yarn.dist.files option in case of yarn-client mode.
> Instead of that, we can have only --files option and pass on the files which
> are present in mapreduce.job.cache.files. While doing so, we make sure that
> spark won't make another copy of the files if files exist on the hdfs. We saw
> the issues when files are getting copied multiple times and causing
> exceptions such as :
> {code}
> Diagnostics: Resource
> hdfs://localhost/user/saley/.sparkStaging/application_1234_123/oozie-examples.jar
> changed on src filesystem
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
