[ https://issues.apache.org/jira/browse/HBASE-12953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326939#comment-14326939 ]
Hadoop QA commented on HBASE-12953: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12699585/HBASE-12953_3.patch against master branch at commit 31f17b17f0e2d12550b97098ec45ab59c5d98d58. ATTACHMENT ID: 12699585 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 4 new or modified tests. {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions (2.4.1 2.5.2 2.6.0) {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 checkstyle{color}. The applied patch does not increase the total number of checkstyle errors {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 lineLengths{color}. The patch does not introduce lines longer than 100 {color:green}+1 site{color}. The mvn site goal succeeds with this patch. {color:red}-1 core tests{color}. The patch failed these unit tests: {color:red}-1 core zombie tests{color}. There are 1 zombie test(s): at org.apache.hadoop.hbase.coprocessor.TestMasterObserver.testRegionTransitionOperations(TestMasterObserver.java:1604) Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//artifact/patchprocess/checkstyle-aggregate.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/12904//console This message is automatically generated. > RegionServer is not functionally working with AysncRpcClient in secure mode > --------------------------------------------------------------------------- > > Key: HBASE-12953 > URL: https://issues.apache.org/jira/browse/HBASE-12953 > Project: HBase > Issue Type: Bug > Components: security > Affects Versions: 2.0.0, 1.1.0 > Reporter: Ashish Singhi > Assignee: stack > Priority: Critical > Fix For: 2.0.0, 1.1.0 > > Attachments: HBASE-12953.patch, HBASE-12953_1.patch, > HBASE-12953_2.patch, HBASE-12953_2.patch, HBASE-12953_2.patch, > HBASE-12953_2.patch, HBASE-12953_2.patch, HBASE-12953_3.patch, > HBASE-12953_3.patch, HBASE-12953_3.patch, testcase.patch > > > HBase version 2.0.0 > Default value for {{hbase.rpc.client.impl}} is set to AsyncRpcClient. > When trying to install HBase with Kerberos, RegionServer is not working > functionally. > The following log is logged in its log file > {noformat} > 2015-02-02 14:59:05,407 WARN [AsyncRpcChannel-pool1-t1] > channel.DefaultChannelPipeline: An exceptionCaught() event was fired, and it > reached at the tail of the pipeline. It usually means the last handler in the > pipeline did not handle the exception. > io.netty.channel.ChannelPipelineException: > org.apache.hadoop.hbase.security.SaslClientHandler.handlerAdded() has thrown > an exception; removed. > at > io.netty.channel.DefaultChannelPipeline.callHandlerAdded0(DefaultChannelPipeline.java:499) > at > io.netty.channel.DefaultChannelPipeline.callHandlerAdded(DefaultChannelPipeline.java:481) > at > io.netty.channel.DefaultChannelPipeline.addFirst0(DefaultChannelPipeline.java:114) > at > io.netty.channel.DefaultChannelPipeline.addFirst(DefaultChannelPipeline.java:97) > at > io.netty.channel.DefaultChannelPipeline.addFirst(DefaultChannelPipeline.java:235) > at > io.netty.channel.DefaultChannelPipeline.addFirst(DefaultChannelPipeline.java:214) > at > org.apache.hadoop.hbase.ipc.AsyncRpcChannel$2.operationComplete(AsyncRpcChannel.java:194) > at > org.apache.hadoop.hbase.ipc.AsyncRpcChannel$2.operationComplete(AsyncRpcChannel.java:157) > at > io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:680) > at > io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:603) > at > io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:563) > at > io.netty.util.concurrent.DefaultPromise.trySuccess(DefaultPromise.java:406) > at > io.netty.channel.DefaultChannelPromise.trySuccess(DefaultChannelPromise.java:82) > at > io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.fulfillConnectPromise(AbstractNioChannel.java:253) > at > io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:288) > at > io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:528) > at > io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468) > at > io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354) > at > io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) > at java.lang.Thread.run(Thread.java:745) > Caused by: javax.security.sasl.SaslException: GSS initiate failed [Caused by > GSSException: No valid credentials provided (Mechanism level: Failed to find > any Kerberos tgt)] > at > com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:212) > at > org.apache.hadoop.hbase.security.SaslClientHandler.handlerAdded(SaslClientHandler.java:154) > at > io.netty.channel.DefaultChannelPipeline.callHandlerAdded0(DefaultChannelPipeline.java:486) > ... 20 more > Caused by: GSSException: No valid credentials provided (Mechanism level: > Failed to find any Kerberos tgt) > at > sun.security.jgss.krb5.Krb5InitCredential.getInstance(Krb5InitCredential.java:147) > at > sun.security.jgss.krb5.Krb5MechFactory.getCredentialElement(Krb5MechFactory.java:121) > at > sun.security.jgss.krb5.Krb5MechFactory.getMechanismContext(Krb5MechFactory.java:187) > at > sun.security.jgss.GSSManagerImpl.getMechanismContext(GSSManagerImpl.java:223) > at > sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:212) > at > sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:179) > at > com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:193) > {noformat} > When set hbase.rpc.client.impl to RpcClientImpl, there seems to be no issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)