Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/7394#issuecomment-121345590
Perhaps I'm missing something but I thought ExecutorDelegationTokenUpdater
just needs the spark.yarn.credentials.file conf setting. in
YarnClientSchedulerBackend we pass the sparkconf into new Client which then in
submitApplication should populate spark.yarn.credentials.file and then you can
use it after submitApplication in YarnClientSchedulerBackend to
SparkHadoopUtil.startExecutorDelegationTokenRenewer.
its very similar to what you have just moving the call from
submitApplication out into YarnClientSchedulerBackend which just seems like a
more logic place to me. Since we already logged in on submission this
shouldn't need to run for a while so we could easily wait to start this like we
do asyncMonitorApplication.
---
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]
