You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Robert Yokota (JIRA)" <ji...@apache.org> on 2016/09/14 23:08:20 UTC
[jira] [Commented] (HBASE-16633) Optimize HBase RPC Encryption
Performance
[ https://issues.apache.org/jira/browse/HBASE-16633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491706#comment-15491706 ]
Robert Yokota commented on HBASE-16633:
---------------------------------------
I've attached a patch. Most of the code is from HADOOP-10768. The patch does not account for {{AsyncHBaseSaslRpcClientHandler}}
> Optimize HBase RPC Encryption Performance
> -----------------------------------------
>
> Key: HBASE-16633
> URL: https://issues.apache.org/jira/browse/HBASE-16633
> Project: HBase
> Issue Type: Bug
> Components: security
> Reporter: Robert Yokota
> Attachments: HBASE-16633.master.001.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)