HubSpot Backport: HADOOP-18583. Fix loading of OpenSSL 3.x symbols (#5256) #58
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…pache#5256) Contributed by Sebastian Klemke
charlesconnell
requested review from
aalhour,
ksravista,
ndimiduk and
rmdmattingly
|
I ran a single DataNode in a large cluster on this branch during a backup. CPU time devoted to AES encryption in the DataNode dropped from 17% to 10% |
ndimiduk
approved these changes
Nov 29, 2024
charlesconnell
requested review from
ksravista
and removed request for
ksravista
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contributed by Sebastian Klemke
Backport of apache#5256 to HubSpot's fork for 3.3.6
This allows Hadoop processes to use the native OpenSSL 3.x libraries installed on Alma Linux 9 machines. This will replace the implementation of AES from the JVM with the one provided by OpenSSL. This will likely reduce the CPU cycles spent doing AES encryption / decryption for Kerberos connections. This isn't a bottleneck for us, so it's not a huge deal, but it's nice.