GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/19074
[SPARK-21714][CORE][BACKPORT-2.2] Avoiding re-uploading remote resources in
yarn client mode
## What changes were proposed in this pull request?
This is a backport PR to fix issue of re-uploading remote resource in yarn
client mode. The original PR is #18962.
## How was this patch tested?
Tested in local UT.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jerryshao/apache-spark
SPARK-21714-2.2-backport
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/19074.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #19074
----
commit 9c5b56247ebc997cf7e8e64cbe95e07ff74bbbe6
Author: jerryshao <[email protected]>
Date: 2017-08-25T16:57:53Z
[SPARK-21714][CORE][YARN] Avoiding re-uploading remote resources in yarn
client mode
With SPARK-10643, Spark supports download resources from remote in client
deploy mode. But the implementation overrides variables which representing
added resources (like `args.jars`, `args.pyFiles`) to local path, And yarn
client leverage this local path to re-upload resources to distributed cache.
This is unnecessary to break the semantics of putting resources in a shared FS.
So here proposed to fix it.
This is manually verified with jars, pyFiles in local and remote storage,
both in client and cluster mode.
Author: jerryshao <[email protected]>
Closes #18962 from jerryshao/SPARK-21714.
(cherry picked from commit 1813c4a8dd4388fe76a4ec772c9be151be0f60a1)
Signed-off-by: jerryshao <[email protected]>
Change-Id: Ib2e8cb056707b362bc1c496002bac1472dc78ea7
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
