[jira] [Created] (HBASE-16563) hbase-assembly can only deal with the first license of dependency
Colin Ma created HBASE-16563:
Summary: hbase-assembly can only deal with the first license of
dependency
Key: HBASE-16563
URL: https://issues.apache.org/jira/browse/HBASE-16563
Project: HBase
Issue Type: Bug
Components: build
Reporter: Colin Ma
Assignee: Colin Ma
Currently, only the first in will be validated in
LICENSE.vm. The hbase-assembly will be failed to validate the following
information,because Apache License v2.0 is not the first one :
{code}
LGPL, version 2.1
http://www.gnu.org/licenses/licenses.html
repo
Apache License v2.0
http://www.apache.org/licenses/LICENSE-2.0.txt
repo
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-16414) Improve performance for RPC encryption with Apache Common Crypto
Colin Ma created HBASE-16414: Summary: 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 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)
[jira] [Created] (HBASE-16192) Fix the potential problems in TestAcidGuarantees
Colin Ma created HBASE-16192: Summary: Fix the potential problems in TestAcidGuarantees Key: HBASE-16192 URL: https://issues.apache.org/jira/browse/HBASE-16192 Project: HBase Issue Type: Bug Reporter: Colin Ma Assignee: Colin Ma Fix For: 2.0.0 The following exception will be thrown in QA runs for TestAcidGuarantees: Caused by: java.lang.RuntimeException: java.lang.OutOfMemoryError: unable to create new native thread at org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithoutRetries(RpcRetryingCallerImpl.java:178) at org.apache.hadoop.hbase.client.ClientScanner.call(ClientScanner.java:316) at org.apache.hadoop.hbase.client.ClientScanner.nextScanner(ClientScanner.java:291) at org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:167) at org.apache.hadoop.hbase.client.ClientScanner.(ClientScanner.java:160) at org.apache.hadoop.hbase.client.ClientSimpleScanner.(ClientSimpleScanner.java:40) at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:366) at org.apache.hadoop.hbase.TestAcidGuarantees$AtomicScanReader.doAnAction(TestAcidGuarantees.java:229) at org.apache.hadoop.hbase.MultithreadedTestUtil$RepeatingTestThread.doWork(MultithreadedTestUtil.java:147) at org.apache.hadoop.hbase.MultithreadedTestUtil$TestThread.run(MultithreadedTestUtil.java:123) Set the hbase.hconnection.threads.max to avoid this failure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-16171) Fix the potential problems in TestHCM.testConnectionCloseAllowsInterrupt
Colin Ma created HBASE-16171: Summary: Fix the potential problems in TestHCM.testConnectionCloseAllowsInterrupt Key: HBASE-16171 URL: https://issues.apache.org/jira/browse/HBASE-16171 Project: HBase Issue Type: Bug Reporter: Colin Ma Assignee: Colin Ma TestHCM.testConnectionCloseAllowsInterrupt is not stable in QA runs, and always failed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-16160) Get the UnsupportedOperationException when using delegation token with encryption
Colin Ma created HBASE-16160: Summary: Get the UnsupportedOperationException when using delegation token with encryption Key: HBASE-16160 URL: https://issues.apache.org/jira/browse/HBASE-16160 Project: HBase Issue Type: Bug Reporter: Colin Ma Assignee: Colin Ma Using delegation token with encryption, when do the Put operation, will get the following exception: [RpcServer.FifoWFPBQ.priority.handler=5,queue=1,port=48345] ipc.CallRunner(161): RpcServer.FifoWFPBQ.priority.handler=5,queue=1,port=48345: caught: java.lang.UnsupportedOperationException at java.nio.ByteBuffer.array(ByteBuffer.java:959) at org.apache.hadoop.hbase.ipc.BufferChain.getBytes(BufferChain.java:66) at org.apache.hadoop.hbase.ipc.RpcServer$Call.wrapWithSasl(RpcServer.java:547) at org.apache.hadoop.hbase.ipc.RpcServer$Call.setResponse(RpcServer.java:467) at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:140) at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:189) at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:169) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-16159) OutOfMemory exception when using AsyncRpcClient with encryption to read rpc response
Colin Ma created HBASE-16159: Summary: OutOfMemory exception when using AsyncRpcClient with encryption to read rpc response Key: HBASE-16159 URL: https://issues.apache.org/jira/browse/HBASE-16159 Project: HBase Issue Type: Bug Reporter: Colin Ma Assignee: Colin Ma Test the Get with encryption AsyncRpcClient with in infinity loop, will get the OOM exception. The root cause is the same as HBASE-16054. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-16054) OutOfMemory exception when use AsyncRpcClient with encryption
Colin Ma created HBASE-16054: Summary: OutOfMemory exception when use AsyncRpcClient with encryption Key: HBASE-16054 URL: https://issues.apache.org/jira/browse/HBASE-16054 Project: HBase Issue Type: Bug Reporter: Colin Ma Assignee: Colin Ma Test the AsyncRpcClient with encryption in infinity loop, will get the OOM exception like the following: io.netty.util.internal.OutOfDirectMemoryError: failed to allocate 29106160 byte(s) of direct memory (used: 2607219760, max: 2609905664) at io.netty.util.internal.PlatformDependent.incrementMemoryCounter(PlatformDependent.java:592) at io.netty.util.internal.PlatformDependent.allocateDirectNoCleaner(PlatformDependent.java:546) at io.netty.buffer.PoolArena$DirectArena.allocateDirect(PoolArena.java:699) at io.netty.buffer.PoolArena$DirectArena.newUnpooledChunk(PoolArena.java:695) at io.netty.buffer.PoolArena.allocateHuge(PoolArena.java:246) at io.netty.buffer.PoolArena.allocate(PoolArena.java:224) at io.netty.buffer.PoolArena.allocate(PoolArena.java:141) at io.netty.buffer.PooledByteBufAllocator.newDirectBuffer(PooledByteBufAllocator.java:262) at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:179) at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:170) at io.netty.buffer.AbstractByteBufAllocator.buffer(AbstractByteBufAllocator.java:107) at org.apache.hadoop.hbase.security.SaslClientHandler.write(SaslClientHandler.java:328) at io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:724) at io.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:716) at io.netty.channel.AbstractChannelHandlerContext.access$1900(AbstractChannelHandlerContext.java:36) at io.netty.channel.AbstractChannelHandlerContext$AbstractWriteTask.write(AbstractChannelHandlerContext.java:1064) at io.netty.channel.AbstractChannelHandlerContext$WriteAndFlushTask.write(AbstractChannelHandlerContext.java:) at io.netty.channel.AbstractChannelHandlerContext$AbstractWriteTask.run(AbstractChannelHandlerContext.java:1049) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:339) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:393) at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:742) at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-15913) Sasl encryption doesn't work with AsyncRpcChannel
Colin Ma created HBASE-15913: Summary: Sasl encryption doesn't work with AsyncRpcChannel Key: HBASE-15913 URL: https://issues.apache.org/jira/browse/HBASE-15913 Project: HBase Issue Type: Bug Reporter: Colin Ma Assignee: Colin Ma The async RPC code in branch-1 will have problems with qop != auth. It's the same as HBASE-15830. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-15830) Sasl encryption doesn't work with AsyncRpcChannelImpl
Colin Ma created HBASE-15830: Summary: Sasl encryption doesn't work with AsyncRpcChannelImpl Key: HBASE-15830 URL: https://issues.apache.org/jira/browse/HBASE-15830 Project: HBase Issue Type: Bug Reporter: Colin Ma Currently, sasl encryption doesn't work with AsyncRpcChannelImpl, there has 3 problems: 1. [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/security/SaslClientHandler.java#L308] will throw the following exception: java.lang.UnsupportedOperationException: direct buffer at io.netty.buffer.UnpooledUnsafeDirectByteBuf.array(UnpooledUnsafeDirectByteBuf.java:199) at org.apache.hadoop.hbase.security.SaslClientHandler.write(SaslClientHandler.java:308) 2. [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/AsyncRpcChannelImpl.java#L212] has deadlocks problem. 3. TestAsyncSecureIPC doesn't cover the sasl encryption test case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
