Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14789
I think there are two different issues, one that is being addressed by this
change and one that is the one Tom and I are talking about:
1. triggering Spark's credential updater mechanism outside its period,
because you want to connect to a new NN or something like that.
1. triggering the credential fetch mechanism from outside the internal
credential updater, which would allow an external entity to update an existing
Spark app's credentials.
The latter is a more complicated change since credential update and fetch
are kinda intertwined right now; for example, for the latter to work, the AM
would also need to fetch the new credentials as if it were an executor, and
right now all the AM do is run the update thread.
So I think this is fine for covering case 1 (caveat: I haven't looked at
the code yet), but it would be nice to have a solution for case 2 eventually.
---
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]
