[HBASE-16633] Optimize HBase RPC Encryption Performance

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: security
• Assignee: Unassigned
• Reporter: Robert Yokota
• Created: 14/Sep/16 22:50
• Updated: 30/Aug/17 21:41
• Resolved: 30/Aug/17 21:41

Description

Similar to HADOOP-10768, when HBase RPC encryption is enabled by setting hbase.rpc.protection to privacy, it does not use AES-NI acceleration by default.

We have implemented a workaround for HBase to use accelerated encryption that can be shown to improve performance, see https://rayokota.wordpress.com/2016/09/13/adventures-in-hardening-hbase/. I will attach a patch of the changes for our workaround, which borrows heavily from the patch for HADOOP-10768, but I'll leave it to the HBase security experts as to what is the best approach.

Issue Links

• is duplicated by: HBASE-16632 Optimize HBase RPC Encryption Performance
• is related to: HBASE-16414 Improve performance for RPC encryption with Apache Common Crypto
• is related to: HDFS-6606 Optimize HDFS Encrypted Transport performance
• is related to: HADOOP-10768 Optimize Hadoop RPC encryption performance