Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17723
@gatorsmile
> Does that mean Mesos plans to use a different solution for delegation
token management?
There's still Mesos code to be added for this; if you trace back through
the JIRA links, Michael submitted a PR earlier that had both this change + the
Mesos code, I just asked him to separate the two.
At the end, both YARN and Mesos code will call into these APIs to create
delegation tokens; there might be some extra code needed in Mesos, since YARN
already has built-in support for managing the initial token set (distribution
and renewal). But creating and distributing new delegation tokens after the TTL
of the initial set should be the same for both.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
