Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/621#issuecomment-42092592
There is no reason to recreate the user and repopulate the
credentials/token unless the credentials/tokens are being updated in the
ExecutorBackend process. On yarn this definitely doesn't happen. Once you
start an executor it keeps the same credentials/tokens, the Yarn
resourcemanager handles renewing the tokens. As far as I know there isn't
support for this built into spark for mesos and standalone but perhaps there is
something I'm not aware of. Is there anything you know of that does that, that
I might have missed? The only other case its useful to create a separate ugi
is if we add support to run tasks as different users.
Thanks for the comments and doing the standalone testing. I'll update.
---
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.
---
