-
Notifications
You must be signed in to change notification settings - Fork 435
TEZ-4600: Secret managers in Tez should respect the algorithm set by hadoop #393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
0a55dc8
to
bd3ed36
Compare
} catch (NoSuchAlgorithmException nsa) { | ||
throw new IllegalArgumentException("Can't find " + algorithm + " algorithm.", nsa); | ||
} catch (InvalidKeyException ike) { | ||
throw new IllegalArgumentException("Invalid key to HMAC computation", ike); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to hardcode HMAC
over here? InvalidKeyException
can be thrown for other algorithms as well, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, right, this is a leftover from the default HMAC-era
This comment was marked as outdated.
This comment was marked as outdated.
🎊 +1 overall
This message was automatically generated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…hadoop Change-Id: I236505c2439ba675f4a277aeb1f7b0faae2d1053
35a7574
to
a060cc4
Compare
🎊 +1 overall
This message was automatically generated. |
changed hadoop enums to strings until TEZ-4607 |
there is a checkstyle warning that has shown up for the unused import, we need to fix it before we merge |
makes sense, I just pushed a commit to remove it |
🎊 +1 overall
This message was automatically generated. |
This PR makes the JobTokenSecretManager in Tez able to use the algorithm specified in:
An additional comment was needed to upgrade to hadoop 3.5.0-SNAPSHOT to compile against the changes of YARN-11738. This PR can be merged once Tez upgraded its hadoop.version to 3.5.0 (which needs a hadoop release first :) )
testing done: turned on SSL shuffle on a cluster having YARN-11738, DAG failed with exceptions mentioned on jira, then with the fix DAG ran successfully (as ShuffleScheduler + ShuffleManager used the non-default algorithm configured)