07-07-2018 09:56 AM
While starting the Hbase thrift sever via CM Mangaer an geeting bellow error:
Cannot locate configuration: tried hadoop-metrics2-hbase.properties,hadoop-metrics2.properties
Scheduled snapshot period at 10 second(s).
HBase metrics system started
07-09-2018 07:48 AM
The log lines provided are not errors and probably don't have anything to do with the server not starting.
Some things to review to identify why the server is not starting:
The stdout.log and stderr.log files for the Hbase Thrift server
In Cloudera Manager, go to Hbase --> Instances --> Hbase Thrift Server
When in the Hbase Thrift Server page, click the "Log Files" drop-down and choose stout.log and stderr.log. Generally, the last lines of the stderr.log file will indicate if the supervisor was able to start up the process or not.
If there are no errors at the bottom of the stderr.log, then it is likely the Hbase Thrift Server started up but then failed for some reason. In this case, you want to have a look at the Hbase Thrift Server logs.
You can also view "Role Log" in the "Log Files" drop down in Cloudera Manager to view the role log. It may be easier to read via the command line, though. If you can, ssh to the host where the Hbase Thrift Server should be running and navigate to /var/log/hbase.
You will see your HBASETHRIFTSERVER log file(s) there and you can review the logs for review.
What is the real problem you see? What observations tell you that the server is having a problem?
07-10-2018 05:09 AM - edited 07-10-2018 05:09 AM
Thanks, thrift server is started.
i want to access Hbase tables using Hue. But when it try to acess it shows API error:
initially it was showing api timeout error:.
then i edited hue.ini file using CM under configuration tab by clicking on advanced property.
and added following path where my hbase-site.xml is located
hbase.regionserver.thrift.http == enabled
hbase.thrift.support.proxyuser = enabled
after saving this its showing api error.
What to Do
07-10-2018 09:41 AM
Thank you for clarifying.
In recent CDH versions, there should be no need to edit the "hbase_conf_dir" value as Cloudera Manager configures that on its own.
I would recommend reverting any changes you made to try to troubleshoot the issue and then recreate it.
Explain exactly what you are clicking on in Hue and what happens so we have some context for helping.
Next, look at the /var/log/hue/runcpserver.log file to see what messages or errors occur when Hue is attempting to connect to the thrift server.
If you are unsure what to do or what the messages show you, share with us your runcpserver.log output that shows time during your attempt to view tables in Hue