[ https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540566#comment-13540566 ]
Andrew Purtell commented on HBASE-7442: --------------------------------------- There's a short term fix here and another one that may take a bit of effort to get right. I don't agree that the second option is "cleaner" but it is more expedient. We could do that as a step toward the surgery Gary suggests. bq. The fact that a single Configuration is fixed in the HBaseClient seems like a broken abstraction as it currently stands. I agree, this is frustrating. > 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 > Fix For: 0.96.0, 0.94.5 > > Attachments: attempt_201212271546_0001_m_000000_0.log, > HBASE-7442-0.92.1.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