[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540472#comment-13540472
]
James Kinley commented on HBASE-7442:
-------------------------------------
Please see attached patch.
The first option was actually quite messy to implement. {{clusterId}} and
{{conf}} are fixed in *{{HBaseClient}}* when it's created and cached by
*{{SecureRpcEngine}}*, so to implement the fix here I would have had to pass
the different cluster {{confs}} up through *{{HConnectionManager}}* and
*{{HBaseRPC}}* in order to override the clusterId in
*{{SecureClient#SecureConnection}}*.
I've gone with the second option of creating and caching different
*{{SecureClients}}* for the local and remote clusters in *{{SecureRpcEngine}}*
- keyed off of the {{clusterId}} instead of the default *{{SocketFactory}}*. I
think this is a cleaner solution.
Please let me know what you think.
> 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
