Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B78059889 for ; Wed, 13 Mar 2013 02:52:15 +0000 (UTC) Received: (qmail 88570 invoked by uid 500); 13 Mar 2013 02:52:15 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 88518 invoked by uid 500); 13 Mar 2013 02:52:15 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 88256 invoked by uid 99); 13 Mar 2013 02:52:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Mar 2013 02:52:14 +0000 Date: Wed, 13 Mar 2013 02:52:14 +0000 (UTC) From: "Hudson (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600747#comment-13600747 ] Hudson commented on HBASE-7442: ------------------------------- Integrated in HBase-TRUNK #3952 (See [https://builds.apache.org/job/HBase-TRUNK/3952/]) HBASE-7482 Port HBASE-7442 HBase remote CopyTable not working when security enabled to trunk (Revision 1455764) Result = FAILURE garyh : Files : * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/ProtobufRpcClientEngine.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableOutputFormat.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/RandomTimeoutRpcEngine.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestDelayedRpc.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestIPC.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestProtoBufRpc.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestHMasterRPCException.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestClusterId.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/security/token/TestTokenAuthentication.java > HBase remote CopyTable not working when security enabled > -------------------------------------------------------- > > Key: HBASE-7442 > URL: https://issues.apache.org/jira/browse/HBASE-7442 > Project: HBase > Issue Type: Bug > Components: IPC/RPC, mapreduce, security > Affects Versions: 0.92.1 > Reporter: James Kinley > Assignee: James Kinley > Fix For: 0.92.3, 0.94.4 > > Attachments: attempt_201212271546_0001_m_000000_0.log, HBASE-7442-0.92.1.patch, HBASE-7442-0.94.patch > > > When security is enabled, HBase CopyTable fails with Kerberos exception: > {code} > FATAL org.apache.hadoop.ipc.SecureClient: SASL authentication failed. The most likely cause is missing or invalid credentials. Consider 'kinit'. > javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)] > {code} > This is only when copying to remote HBase cluster (using either MRv1 or YARN), local copy works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira