Github user harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/7394#discussion_r34819436
--- Diff:
yarn/src/main/scala/org/apache/spark/scheduler/cluster/YarnClientSchedulerBackend.scala
---
@@ -61,6 +60,12 @@ private[spark] class YarnClientSchedulerBackend(
// to the executors
super.start()
+ // SPARK-8851: In yarn-client mode, the AM still does the credentials
refresh. The driver
+ // reads the credentials from HDFS, just like the executors and
updates its own credentials
+ // cache.
+ if (conf.contains("spark.yarn.credentials.file")) {
+ YarnSparkHadoopUtil.get.startExecutorDelegationTokenRenewer(conf)
+ }
waitForApplication()
--- End diff --
Will do. This might not be that big an issue since the app is likely to be
submitted and `waitForApplication` returned before we need the tokens to be
updated (wouldn't this cause bigger issues otherwise - like the executors might
not be able to start/read HDFS data because the tokens already expired etc?).
Basically this just means that the token expiry interval is too short to be
useful/
---
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]
