Uh oh!
There was an error while loading. Please reload this page.
TEZ-4600: Secret managers in Tez should respect the algorithm set by hadoop - #393
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
| } 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.
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.
oh, right, this is a leftover from the default HMAC-era
This comment was marked as outdated.
This comment was marked as outdated.
tez-yetus
commented
Feb 25, 2025
🎊 +1 overall
This message was automatically generated. |
abstractdog
commented
Feb 25, 2025
…hadoop Change-Id: I236505c2439ba675f4a277aeb1f7b0faae2d1053
tez-yetus
commented
Feb 26, 2025
🎊 +1 overall
This message was automatically generated. |
abstractdog
commented
Feb 26, 2025
changed hadoop enums to strings until TEZ-4607 |
ayushtkn
commented
Mar 3, 2025
there is a checkstyle warning that has shown up for the unused import, we need to fix it before we merge |
abstractdog
commented
Mar 4, 2025
makes sense, I just pushed a commit to remove it |
tez-yetus
commented
Mar 4, 2025
🎊 +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)