sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SQOOP-599) Import to HBase is not working on secure cluster
Date Tue, 11 Sep 2012 09:22:07 GMT
Jarek Jarcec Cecho created SQOOP-599:
----------------------------------------

             Summary: Import to HBase is not working on secure cluster
                 Key: SQOOP-599
                 URL: https://issues.apache.org/jira/browse/SQOOP-599
             Project: Sqoop
          Issue Type: Bug
          Components: hbase-integration
    Affects Versions: 1.4.2
            Reporter: Jarek Jarcec Cecho
            Assignee: Jarek Jarcec Cecho
             Fix For: 1.4.3


HBase import will fail on secure cluster:

{code}
12/09/06 03:29:32 INFO mapred.JobClient: Task Id : attempt_201209041259_0575_m_000003_0, Status
: FAILED
java.lang.RuntimeException: SASL authentication failed. The most likely cause is missing or
invalid credentials. Consider 'kinit'.
	at org.apache.hadoop.hbase.ipc.SecureClient$SecureConnection$1.run(SecureClient.java:242)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:396)
	at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1332)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.hadoop.hbase.util.Methods.call(Methods.java:37)
	at org.apache.hadoop.hbase.security.User.call(User.java:586)
	at org.apache.hadoop.hbase.security.User.access$700(User.java:50)
	at org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:440)
	at org.apache.hadoop.hbase.ipc.Se
{code}

--
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

Mime
View raw message