hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Ma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16414) Improve performance for RPC encryption with Apache Common Crypto
Date Thu, 08 Sep 2016 07:23:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15473072#comment-15473072
] 

Colin Ma commented on HBASE-16414:
----------------------------------

[~ram_krish], can you help to review the new patch? The ConnectionHeaderResponse is added
to process the any negotiation after connection setup. The [review board|https://reviews.apache.org/r/51089/]
is also update.
For the errors from HADOOP QA, I'm not sure the root cause of mvninstall for hbase-server
and hbase-client, everything works fine in my local. The whitespace is auto generated with
protobuf, I think it can be ignored.
Thanks for your help.

> Improve performance for RPC encryption with Apache Common Crypto
> ----------------------------------------------------------------
>
>                 Key: HBASE-16414
>                 URL: https://issues.apache.org/jira/browse/HBASE-16414
>             Project: HBase
>          Issue Type: Improvement
>          Components: IPC/RPC
>    Affects Versions: 2.0.0
>            Reporter: Colin Ma
>            Assignee: Colin Ma
>         Attachments: HBASE-16414.001.patch, HBASE-16414.002.patch, HBASE-16414.003.patch,
HBASE-16414.004.patch, HbaseRpcEncryptionWithCrypoto.docx
>
>
> Hbase RPC encryption is enabled by setting “hbase.rpc.protection” to "privacy". With
the token authentication, it utilized DIGEST-MD5 mechanisms for secure authentication and
data protection. For DIGEST-MD5, it uses DES, 3DES or RC4 to do encryption and it is very
slow, especially for Scan. This will become the bottleneck of the RPC throughput.
> Apache Commons Crypto is a cryptographic library optimized with AES-NI. It provides Java
API for both cipher level and Java stream level. Developers can use it to implement high performance
AES encryption/decryption with the minimum code and effort. Compare with the current implementation
of org.apache.hadoop.hbase.io.crypto.aes.AES, Crypto supports both JCE Cipher and OpenSSL
Cipher which is better performance than JCE Cipher. User can configure the cipher type and
the default is JCE Cipher.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message