Troubleshooting

When using the HBase connector, you might encounter errors that can be fixed by troubleshooting and adjusting values for properties or configuration.

Connection errors

You might encounter the following errors:

Table 1. Connection errors

Error type	Error details	Troubleshooting details
Connection times out. Caused by KrbException with status code 7	Connector crashes with Connection failed: org.apache.hadoop.hbase.client.RetriesExhaustedException Caused by: javax.security.sasl.SaslException: GSS initiate failed [Caused by org.ietf.jgss.GSSException, major code: 11, minor code: 0 major string: General failure, unspecified at GSSAPI level minor string: Error: java.lang.Exception: Error: com.ibm.security.krb5.KrbException, status code: 7 message: LOOKING_UP_SERVER:hbase/X.X.X.X@IBM.COM] Status code 7 means such server was not found in Kerberos database. Kerberos service principal should be name/fully.qualified.domain.name@REALM. Presence of IP address instead of FQDN indicates broken or missing DNS configuration	You must be able to resolve hostname from ip address. Add or update DNS records to map IP address that is causing the error to its hostname. Alternatively add an entry witH ip and fqdn to /etc/hosts file on each node.
Connector crashes with NoClassDefFoundError	Connector crashes with java.lang.NoClassDefFoundError: MissingClass. This error indicates that some class is missing from your classpath.	You must locate which jar file contains required class. Login to any machine on the target cluster and run find / -name "*.jar" | xargs grep <MissingClass> from the command line. Include the matching jar in the classpath. If multiple versions are found, use the highest one.