Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8942#issuecomment-149671639
Hmm, so looking at the FileSystem cache code it creates a new key that
stores:
this.ugi = UserGroupInformation.getCurrentUser();
So if the current user changes from when first filesystem is created to
when we run then it would have this problem.
on the client side I don't think we do any specific runAsUser calls but
perhaps its an issue with the keytab login and the user already logged in.
So perhaps it makes sense to do something like this PR but I would rather
see it a if/else type thing where in the code we either login from keytab or we
grab the tokens that way we don't end up with 2 different methods of login and
we don't accidentally break things if order of things change.
---
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]
