[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601085#comment-13601085
]
Hudson commented on HBASE-7442:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #445 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/445/])
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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601122#comment-13601122
]
Hudson commented on HBASE-7442:
---
Integrated in hbase-0.95-on-hadoop2 #24 (See
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/24/])
HBASE-7482 Port HBASE-7442 HBase remote CopyTable not working when security
enabled to trunk (Revision 1455765)
Result = FAILURE
garyh :
Files :
*
/hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
*
/hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java
*
/hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/ProtobufRpcClientEngine.java
*
/hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableOutputFormat.java
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/RandomTimeoutRpcEngine.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestDelayedRpc.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestIPC.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestProtoBufRpc.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestHMasterRPCException.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestClusterId.java
*
/hbase/branches/0.95/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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13600742#comment-13600742
]
Hudson commented on HBASE-7442:
---
Integrated in hbase-0.95 #67 (See
[https://builds.apache.org/job/hbase-0.95/67/])
HBASE-7482 Port HBASE-7442 HBase remote CopyTable not working when security
enabled to trunk (Revision 1455765)
Result = FAILURE
garyh :
Files :
*
/hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
*
/hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java
*
/hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/ProtobufRpcClientEngine.java
*
/hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableOutputFormat.java
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/RandomTimeoutRpcEngine.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestDelayedRpc.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestIPC.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestProtoBufRpc.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestHMasterRPCException.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestClusterId.java
*
/hbase/branches/0.95/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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1351#comment-1351
]
Hudson commented on HBASE-7442:
---
Integrated in HBase-0.94-security-on-Hadoop-23 #10 (See
[https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/10/])
HBASE-7442 HBase remote CopyTable not working when security enabled (James
Kinley) (Revision 1428119)
Result = FAILURE
larsh :
Files :
*
/hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureRpcEngine.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13544556#comment-13544556
]
Hudson commented on HBASE-7442:
---
Integrated in HBase-0.92-security #147 (See
[https://builds.apache.org/job/HBase-0.92-security/147/])
HBASE-7442 HBase remote CopyTable not working when security enabled (James
Kinley) (Revision 1428151)
Result = FAILURE
tedyu :
Files :
*
/hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureRpcEngine.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13542558#comment-13542558
]
Lars Hofhansl commented on HBASE-7442:
--
+1 0.94. Ted, you want this in 0.92?
I'll commit to 0.94, unless I hear objections soon.
I want to reroll the RC, so let's make a forward port jira for 0.96.
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.92.3, 0.96.0, 0.94.5
Attachments: attempt_201212271546_0001_m_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13542587#comment-13542587
]
Lars Hofhansl commented on HBASE-7442:
--
What about 0.92.3, Ted?
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.92.3, 0.94.4
Attachments: attempt_201212271546_0001_m_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13542588#comment-13542588
]
Ted Yu commented on HBASE-7442:
---
Will soon integrate to 0.92 :-)
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.92.3, 0.94.4
Attachments: attempt_201212271546_0001_m_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13542592#comment-13542592
]
Lars Hofhansl commented on HBASE-7442:
--
Committed to 0.94. Thanks for the patch, James.
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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13542651#comment-13542651
]
Hudson commented on HBASE-7442:
---
Integrated in HBase-0.94 #693 (See
[https://builds.apache.org/job/HBase-0.94/693/])
HBASE-7442 HBase remote CopyTable not working when security enabled (James
Kinley) (Revision 1428119)
Result = FAILURE
larsh :
Files :
*
/hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureRpcEngine.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13542684#comment-13542684
]
Ted Yu commented on HBASE-7442:
---
Integrated to 0.92 branch as well.
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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13542725#comment-13542725
]
Hudson commented on HBASE-7442:
---
Integrated in HBase-0.92 #610 (See
[https://builds.apache.org/job/HBase-0.92/610/])
HBASE-7442 HBase remote CopyTable not working when security enabled (James
Kinley) (Revision 1428151)
Result = FAILURE
tedyu :
Files :
*
/hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureRpcEngine.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13542776#comment-13542776
]
Hudson commented on HBASE-7442:
---
Integrated in HBase-0.94-security #93 (See
[https://builds.apache.org/job/HBase-0.94-security/93/])
HBASE-7442 HBase remote CopyTable not working when security enabled (James
Kinley) (Revision 1428119)
Result = SUCCESS
larsh :
Files :
*
/hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureRpcEngine.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13540937#comment-13540937
]
Gary Helmling commented on HBASE-7442:
--
Agree on both the need for a short term fix and moving the bigger refactoring
into another JIRA. I'll open up a new issue.
On the short term fix, I agree with Andy that the change to key the ClientCache
by cluster ID isn't the cleanest fix, but is the most expedient approach for
now.
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.92.3, 0.96.0, 0.94.5
Attachments: attempt_201212271546_0001_m_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13540559#comment-13540559
]
Gary Helmling commented on HBASE-7442:
--
Making the cluster ID should be part of the ConnectionId makes sense (it's part
of the identification of the remote cluster). But I think it's addressing only
part of the problem. Going through this code, it seems like we have a lot of
mismatch between the higher layers and the lower layers, with too much
abstraction in between. At the lower layers, most of the ClientCache stuff
seems completely unused. We currently effectively have an HBaseClient
singleton (for SecureClient as well in 0.92/0.94) in the client code, as I
don't see anything that calls the constructor or RpcEngine.getProxy() versions
with a non-default socket factory. So a lot of the code around this seems like
built up waste.
The fact that a single Configuration is fixed in the HBaseClient seems like a
broken abstraction as it currently stands. In addition to cluster ID, other
configuration parameters (max retries, retry sleep) are fixed at time of
construction. The more I look at the code, the more it looks like the
ClientCache and sharing the HBaseClient instance is an unnecessary
complication. Why cache the HBaseClient instances at all? In
HConnectionManager, we already have a mapping from Configuration to
HConnection. It seems to me like each HConnection(Implementation) instance
should have it's own HBaseClient instance, doing away with the ClientCache
mapping. This would keep each HBaseClient associated with a single
cluster/configuration and fix the current breakage from reusing the same
HBaseClient against different clusters.
Of course, this would become a larger refactoring, probably reworking some of
the HBaseRPC and RpcEngine methods to allow this. Off hand, we might want to
expose a separate RpcEngine.getClient() method that returns a new RpcClient
interface (implemented by HBaseClient) and move the
RpcEngine.getProxy()/stopProxy() implementations into the client. So all proxy
invocations can go through the same client, without requiring the static client
cache. I haven't fully thought this through, so I could be missing other
important aspects. But that approach at least seems like a step in the right
direction for fixing the client abstractions.
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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13540567#comment-13540567
]
Ted Yu commented on HBASE-7442:
---
Nice writeup, Gary.
I think the above analysis deserves its own JIRA.
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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13540618#comment-13540618
]
James Kinley commented on HBASE-7442:
-
Agreed, this would be a short term fix and more refactoring work is required to
get it right. I agree with Ted that this work warrants its own JIRA.
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_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13540628#comment-13540628
]
Lars Hofhansl commented on HBASE-7442:
--
Patch looks good to me. Does it work? :)
Could you make a 0.94 (probably identical to the 0.92 version) and a trunk
version too?
(If we have a 0.94 patch soon, I'll pull it into 0.94.4)
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.92.3, 0.96.0, 0.94.5
Attachments: attempt_201212271546_0001_m_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13540007#comment-13540007
]
James Kinley commented on HBASE-7442:
-
To give some context for the attached log
({{attempt_201212271546_0001_m_00_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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13540031#comment-13540031
]
James Kinley commented on HBASE-7442:
-
I noticed that *{{CopyTable#createSubmittableJob}}*, and specifically
*{{TableMapReduceUtil#initCredentials}}* was only acquiring a delegation token
for the local HBase cluster so I added the following to
*{{TableMapReduceUtil#initCredentials}}*:
{code}
String quorumAddress =
job.getConfiguration().get(TableOutputFormat.QUORUM_ADDRESS);
if (quorumAddress != null) {
String[] parts = ZKUtil.transformClusterKey(quorumAddress);
Configuration peerConf = HBaseConfiguration.create(job.getConfiguration());
peerConf.set(HConstants.ZOOKEEPER_QUORUM, parts[0]);
peerConf.set(hbase.zookeeper.client.port, parts[1]);
peerConf.set(HConstants.ZOOKEEPER_ZNODE_PARENT, parts[2]);
User.getCurrent().obtainAuthTokenForJob(peerConf, job);
}
{code}
The user now has the correct tokens:
Cluster 1 ID = 7bb01c84-3c66-49ca-82d2-2f9218f13dad
Cluster 2 ID = d4653a37-83df-4929-b950-e03987c3b4e8
{code}
INFO token.TokenUtil: Obtained token HBASE_AUTH_TOKEN for user
kinley/ad...@kinley.com on cluster 7bb01c84-3c66-49ca-82d2-2f9218f13dad
INFO token.TokenUtil: Obtained token HBASE_AUTH_TOKEN for user
kinley/ad...@kinley.com on cluster d4653a37-83df-4929-b950-e03987c3b4e8
{code}
But when initialising the *{{HTable}}* connection in the mapper, the
*{{TokenSelector}}* in *{{SecureClient#SecureConnection}}* returns the wrong
token from the user's token cache. This is because the token cache is keyed on
{{clusterId}}, and despite the token for the local cluster existing in the
cache ({{key=7bb01c84-3c66-49ca-82d2-2f9218f13dad}}), the {{clusterId}} is
fixed at this point in *{{HBaseClient}}* to the remote cluster's ID
({{key=d4653a37-83df-4929-b950-e03987c3b4e8}}), and it is this ID that is
always passed to the *{{TokenSelector}}*.
I can think of a couple of possible solutions:
1. Either pass the {{clusterId}} into *{{SecureClient#SecureConnection}}* as
part of the *{{ConnectionId}}*. This way it can be used by the
*{{TokenSelector}}* instead of the fixed ID in the parent class
*{{HBaseClient}}*?, or
2. *{{SecureRpcEngine}}* caches multiple clients based on a
*{{SocketFactory}}*, so we could maintain separate clients for both the local
and remote clusters here?
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
Attachments: attempt_201212271546_0001_m_00_0.log
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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13540051#comment-13540051
]
Lars Hofhansl commented on HBASE-7442:
--
Thanks James.
[~apurtell], [~ghelmling] any thoughts?
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_00_0.log
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
[jira] [Commented] (HBASE-7442) HBase remote CopyTable not working when security enabled
[
https://issues.apache.org/jira/browse/HBASE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13540152#comment-13540152
]
Andrew Purtell commented on HBASE-7442:
---
Thanks for identifying the problem. We should fix this (incorrect) assumption
made in the client code. I don't have a strong opinion but I like option #1
better: for the sake of simplicity a connection to a regionserver is handled
(and cached) the same way whether it is the local cluster or remote.
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_00_0.log
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
