[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540007#comment-13540007
]
James Kinley commented on HBASE-7442:
-------------------------------------
To give some context for the attached log
({{attempt_201212271546_0001_m_000000_0.log}}).
I have setup 2 clusters:
Cluster 1 has two nodes running the following services:
one.kinley.com: HDFS, MRv1
two.kinley.com: HBase, ZK
Cluster 2 has a single node running the following:
three.kinley.com: HDFS, HBase, ZK
Security is enabled on both clusters and all principals are in the same realm
(so cross-realm support is not required).
I'm trying to copy an HBase table from cluster 1 to cluster 2:
{code}
two.kinley.com:~$ hbase org.apache.hadoop.hbase.mapreduce.CopyTable
-Dmapred.child.java.opts="-Dsun.security.krb5.debug=true"
-Dmapred.map.child.log.level=DEBUG --peer.adr=three.kinley.com:2181:/hbase
--new.name=Converged-headers Converged-headers
{code}
Running a local2local CopyTable on cluster 1 and 2 works ok.
> 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
>
> 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
