This issue could be caused by the Hive metastore. First, check if the Impala cataolog server is listening on port 23030 and 2600. If not, you may have a same problem as mine. For my case, I guess that the Impala catalog server keeps trying to connect Hive metastore, but not successfully. The timeout setting for this connection effort seems to be several hours. During this period, the catalog server will not listen to port 23020 and 26000. Therefore, the Impala statestore cannot establish the connection with the catalog server, which leads to the failure of the health test. Sometime, the health test will pass after several hours. But it does not mean that everything is OK. Actually (I guess), the Catalog server just gives up trying, and move ahead to start its service. Therefore, the statestore server can establish the connection with it. But when you excute some queries, Impala will report errors. To fix this problem, you have to solve the Hive metastore issues, or just rebuilt it. The following links give some details on that, https://issues.cloudera.org/browse/IMPALA-2045 http://www.cloudera.com/documentation/archive/cdh/4-x/4-2-0/CDH4-Installation-Guide/cdh4ig_topic_18_4.html
... View more
Hello, all, I am new here, I would like to build my own Cloudera lab. I have bought some retired servers and worked on the first one. I have installed CentOS 6 as the OS. I followed the instructions from the link "http://www.cloudera.com/content/www/en-us/documentation/manager/5-1-x/Cloudera-Manager-Installation-Guide/Cloudera-Manager-Installation-Guide.html" and chose installation path A. It said that the installation was completed but when I open the cloudera manager, I saw an empty page(please see the attached picture), I used the IP address to access, it was still empty. So I tried the installation path B, after serveral steps I still saw the empty page. I have limited Linux knowledge, so it became very hard for me to do the troubleshooting. can anyone here give me some ideas. Many thanks!!!
... View more