[
https://issues.apache.org/jira/browse/SPARK-25689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765477#comment-17765477
]
RickyMa commented on SPARK-25689:
---------------------------------
I've added a follow up pull request for this issue:
https://github.com/apache/spark/pull/42890
> Move token renewal logic to driver in yarn-client mode
> ------------------------------------------------------
>
> Key: SPARK-25689
> URL: https://issues.apache.org/jira/browse/SPARK-25689
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core, YARN
> Affects Versions: 2.4.0
> Reporter: Marcelo Masiero Vanzin
> Assignee: Marcelo Masiero Vanzin
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.0.0
>
>
> Currently, both in yarn-cluster and yarn-client mode, the YARN AM is
> responsible for renewing delegation tokens. That differs from other RMs
> (Mesos and later k8s when it supports this functionality), and is one of the
> roadblocks towards fully sharing the same delegation token-related code.
> We should look at keeping the renewal logic within the driver in yarn-client
> mode. That would also remove the need to distribute the user's keytab to the
> AM when running in that particular mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
