GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/18617
[SPARK-21376][YARN] Fix yarn client token expire issue when cleaning the
staging files in long running scenario
## What changes were proposed in this pull request?
This issue happens in long running application with yarn cluster mode,
because yarn#client doesn't sync token with AM, so it will always keep the
initial token, this token may be expired in the long running scenario, so when
yarn#client tries to clean up staging directory after application finished, it
will use this expired token and meet token expire issue.
## How was this patch tested?
Manual verification is secure cluster.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jerryshao/apache-spark SPARK-21376
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/18617.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 #18617
----
commit 11a14a36734806c150b2f7855badc5f18e30490c
Author: jerryshao <[email protected]>
Date: 2017-07-13T04:00:00Z
make sure client process could clean the staging files without getting
token expire issue
Change-Id: I851f829d38ab93a4caafb7ca029d34da76f92f76
----
---
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]
