You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/08/20 23:11:45 UTC

[jira] [Created] (HBASE-14276) NPE when setting up stub for connection to master if secure connect is refused

Andrew Purtell created HBASE-14276:
--------------------------------------

             Summary: NPE when setting up stub for connection to master if secure connect is refused
                 Key: HBASE-14276
                 URL: https://issues.apache.org/jira/browse/HBASE-14276
             Project: HBase
          Issue Type: Bug
            Reporter: Andrew Purtell
            Priority: Minor
             Fix For: 0.98.15


If an insecure client contacts a secure cluster we can get an NPE when setting up the stub for the master connection. This can happen if auth tokens are not passed correctly to a mapreduce job and obscures the true cause. We should throw an IOException with a clear message, and not retry if possible to distinguish this case.

Found in 0.98 but might be relevant for later branches

{noformat}
Aug 20, 2015 12:04:31 AM org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper <init>
INFO: Process identifier=hconnection-0x3c1e23ff connecting to ZooKeeper ensemble=x.x.x.x:2181,x.x.x.x:2181,x.x.x.x:2181
Aug 20, 2015 12:04:31 AM org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation makeStub
INFO: getMaster attempt 1 of 35 failed; retrying after sleep of 100, exception=com.google.protobuf.ServiceException: java.lang.NullPointerException
Aug 20, 2015 12:04:31 AM org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation makeStub
INFO: getMaster attempt 2 of 35 failed; retrying after sleep of 200, exception=com.google.protobuf.ServiceException: java.io.IOException: Call to xxxx/x.x.x.x:60000 failed on local exception: java.io.EOFException
Aug 20, 2015 12:04:31 AM org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation makeStub
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)