03-16-2016 12:25 PM
Your best bet to figure out why it's failing is to check the log for the RegionServer role. Click on the HBase service and down the left hand side you'll see the RegionServer. You'll want to open that, go to the "Processes" tab, and the click "See Role Log Details". Most recent messages will be at the bottom, and my guess is the error should be in the last few entries. (I might be missing a link or tab or something in that navigation - hopefully this is clear enough for you to find it!)
03-16-2016 12:27 PM
One possibility to have in mind is memory issues. The VM is a very compact environment, and it only gets tested with fairly small demo datasets. If you've loaded other data into HBase prior to trying to access it via Phoenix, you might need to do some tweaking of memory configuration in HBase or add more memory to the VM to get it to work as reliably as it ordinarily would.
03-16-2016 04:43 PM
I do not see any errors in the logs, Region Server Logs are full of just INFO statements, no ERROR, FATAL etc. There were couple of benign WARNs
I tried to follow the steps mentioned in the
And kept having issues with query
hbase(main):001:0> disable 'SYSTEM.SEQUENCE'
ERROR: Connection refused
Here is some help for this command:
Start disable of named table:
hbase> disable 't1'
hbase> disable 'ns1:t1'
03-20-2016 10:13 PM
This is what worked for me.
Increased the Region Server heap size it to 500 MiB, redeployed client configuration and restarted HBase.
I was able to get sql line phoenix script working for me.