本文介绍了Cloudera SCM Manager中Agent失去连接的问题解决方法，包括如何重启Agent服务及应对因/var/log目录满导致的问题。同时，针对HBase Shell挂起的问题提供了详细的排查步骤，如检查HBase Master和Region Server的状态、正确部署客户端配置等。
Q1
Sometimes SCM manger lose connection with agent because the agent is dead.
A1
You should start the agent service.
$cd /etc/init.d
$./cloudera-scm-agent status
$./cloudera-scm-agent start
Cloudera distribution (CDH3 & CDH4) uses an agnet to control and monitor nodes. If the agent stop working, all services should 'Bad' health and it cannot be restarted thru Cloudera Manager.
Cloudera agent can be crushed, when /var/log directory is full.
Clean up /var/log to avoid this issue.
Q2
Hbase Shell Hanging
A2
First thing to check on cloudera manager if there is master and region server status are fine. In this case, there was two hbase master was running. I delete all instances of hbase and created the hbase master and RS instances again. NOw there was one master and 3 RS. Second, when you are accessing the cluster machine to run the hbase shell, ensure to " deploy client configuration" from the "Services" menu. If you are accessing the hbase from other server, ensure to download the configuration files and unzip it and set HBASE_CONF_DIR to that unzip directory. That will ensure that you are pointing to right hbase configuration..
扫一扫
2964
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
