Yes, the Phoenix Query Server is going to act the same as a normal client. Have you changed anything on the system over a standard installation? PQS is unable to find a class which is should find in the hbase-protocol.jar NoClassDefFoundError: Could not initialize class org.apache.hadoop.hbase.protobuf.ProtobufUtil. Please inspect the classpath of PQS and ensure that it is referencing the jar correctly. ... View more

Wherever you configured them to be stored. It defaults to the standard log directory on Linux: /var/log/hbase ... View more

You can try to increase the log level to DEBUG for HBase and look at the RegionServer's log which your receive the Connection closing error from. This is likely the HBase server denying your RPC for some reason. There should be a DEBUG message which informs you why the RPC was rejected. ... View more

Check the state of the RegionServer before the Master reports this error. The Master is trying to read the hbase:meta table and failing. This should be a very fast operation. ... View more

Sorry, this is a pain point that HBase has been trying to unravel for a while now. There isn't a good answer because the protobufs must match between client and server (that's why the trivial shading doesn't work). gRPC hasn't been too common in the HBase realm (at least from my point of view). Until we can get these changes into an Apache release and/or HDP release, you would have to find some way to isolate the conflicting protobuf versions. ... View more

There is https://issues.apache.org/jira/browse/HBASE-15638 which is slated for Apache HBase 2.0 which will shade protobuf as well, but this has not yet been released. ... View more

There is a shaded HBase client which you can try to use. I'm not sure if that will work around conflicting protocol buffer versions though. ... View more