Member since
07-30-2013
509
Posts
113
Kudos Received
124
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2624 | 07-09-2018 11:54 AM | |
2206 | 05-03-2017 11:03 AM | |
5136 | 03-28-2017 02:27 PM | |
1976 | 03-27-2017 03:17 PM | |
1748 | 03-13-2017 04:30 PM |
11-06-2014
11:17 AM
Impala is part of CDH 5. So to upgrade impala, you upgrade all of CDH. You don't upgrade CDH "first". That's the only step. Be sure to follow the Cloudera Manager documentation for upgrades, as CDH5.2 has special upgrade steps. First upgrade Cloudera Manager: http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_ag_upgrading_cm.html Then upgrade CDH: http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_mc_upgrade_to_cdh52.html
... View more
10-23-2014
10:45 AM
Glad that fixed it for you! I've filed an internal bug report to make the upgrade code handle a missing management service. I'm not sure why Sentry should have any issue. If you'd like us to take a look, please start a new thread with more information on the problematic behavior and error messages. Thanks, Darren
... View more
09-19-2014
03:25 PM
Knowledge article 2940 has been created.
... View more
09-15-2014
10:38 PM
Thanks for your reply dlo.
... View more
09-15-2014
06:23 AM
Thanks for your reply dlo.
... View more
09-11-2014
08:26 AM
The problem has been resolved by deleting Hive service and adding it back. The health test of HMS failed initially - the metastore canary failed to drop the table it created. Then it became good after a few minutes. The "show tables" command works in the Hive shell now. The only mistake or cause I can think of is that we started panic after seeing the red/bad health test result right after the install. Then, we troubleshot and edited hive-site.xml by following Configuring the Hive Metastore instruction in the CDH installation guide, which is not necessary and probably caused the issue.
... View more
09-11-2014
07:47 AM
Thanks a lot Darren, a very simple solution 🙂
... View more
09-10-2014
10:12 AM
Hi Bart, There's not really a problem here. Hive emits that warning, but we've found that in some cases setting metastore.local will avoid bugs (specifically when running on postgresql). So better to have the warning than to have the bug. This might help explain the process directory where you're finding all of those hive-site.xml files: http://blog.cloudera.com/blog/2013/07/how-does-cloudera-manager-work/ CM will automatically generate the metastore uris property based on the configured Hive Metastore Server role's host and port. Unless you have "Bypass Hive Metastore Server" selected, CM will emit the metastore uris property in all client configuration (/etc/hive/conf/hive-site.xml) and all dependent services (impala, hue, etc) that need to talk to Hive. The hive deprecation warning is thrown whether or not the metastore uris are configured. So you should just ignore this error. Thanks, Darren
... View more
09-05-2014
02:01 PM
I tested and worked! Thanks a lot! What i used is the function below: reate_hdfs_tmp(self) source code Create the /tmp directory in HDFS with appropriate ownership and permissions. Returns: Reference to the submitted command Since: API v2
... View more
09-05-2014
07:47 AM
Glad you solved this! Keep in mind that when using the symlink, you may need to re-create it whenever you upgrade your cloudera-scm-server-db package in the future, since the symlink confuses the packaging code. Thanks, Darren
... View more