Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.8.0
-
None
Description
Turns out KMS delegation token renewal feature (HADOOP-13155) does not work well with client side impersonation.
In a MR example, an end user (UGI:user) gets all kinds of DTs (with renewer=yarn), and pass them to Yarn. Yarn's resource manager (UGI:yarn) then renews these DTs as long as the MR jobs are running. But currently, the token is used at the kms server side to decide the renewer, in which case is always the token's owner. This ends up rejecting the renew request due to renewer mismatch.
Attachments
Attachments
Issue Links
- Blocked
-
YETUS-420 Hadoop post commit failure due to Docker unable to build image
- Resolved
-
HADOOP-13228 Add delegation token to the connection in DelegationTokenAuthenticator
- Resolved
- depends upon
-
HADOOP-13155 Implement TokenRenewer to renew and cancel delegation tokens in KMS
- Resolved