GitHub user jerryshao opened a pull request:

    https://github.com/apache/spark/pull/14789

    [SPARK-17209][YARN] Add the ability to manually update credentials for 
Spark running on YARN

    ## What changes were proposed in this pull request?
    
    This PR propose to add a new API in `SparkHadoopUtil` to trigger manual 
credential updating in the run-time.
    
    This is mainly used in long running spark applications which needs to 
access different secured system in the run-time. For example, when Zeppelin / 
Spark Shell needs to access different secured HBase cluster or Hive metastore 
service in the run-time, it requires tokens from new services and updates to 
executors immediately. Previously either we need to relaunch the application to 
get new tokens, or we need to wait until the old tokens to expire to get new 
ones. 
    
    With this new API, user could manually trigger credential updating in the 
run-time when required. Credentials will be renewed in AM and updated in 
executor and driver side.
    
    ## How was this patch tested?
    
    Manually verified in the secured cluster.
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jerryshao/apache-spark SPARK-17209

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/14789.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 #14789
    
----
commit 841bec0dfae79ecfce5dc535949879f397313736
Author: jerryshao <[email protected]>
Date:   2016-08-24T07:12:22Z

    Support manual credential update

commit 85370e787b719136cc97cfc358f0e50c55582bb8
Author: jerryshao <[email protected]>
Date:   2016-08-24T13:23:36Z

    Change the comments

----


---
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]

Reply via email to