Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Won't Fix
-
None
-
None
-
None
-
None
Description
If an insecure client contacts a secure cluster we can get an NPE when setting up the stub for the master connection. 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
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