Member since
07-30-2013
509
Posts
113
Kudos Received
124
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2626 | 07-09-2018 11:54 AM | |
2206 | 05-03-2017 11:03 AM | |
5141 | 03-28-2017 02:27 PM | |
1976 | 03-27-2017 03:17 PM | |
1748 | 03-13-2017 04:30 PM |
08-15-2014
11:12 AM
This can also happen if you have insufficient disk space in /opt/cloudera/ As Gautam said, agent logs should indicate the error.
... View more
08-14-2014
11:11 AM
The upgrade guide should include instructions for offline installs. If it doesn't, check the install guides.
... View more
08-13-2014
09:46 PM
Sorry I didn't realize this earlier, but the problem is you are using a version of CM that only works with Impala < 1.2. You'll need to upgrade to CM 4.8 or higher in order to use Impala 1.2 or higher. This is because Impala introduced a new role, the Catalog Server, in Impala 1.2, and Cloudera Manager < 4.8 didn't know about it. Note that CM 5.x works just fine with CDH 4. Be sure to follow the appropriate upgrade documentation when performing your upgrade. For the lastest CM version, you'll want to start reading here, then click on "Upgrading Cloudera Manager 4 to Cloudera Manager 5": http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM5/latest/Cloudera-Manager-Administration-Guide/cm5ag_upgrading_cm.html Thanks, Darren
... View more
08-13-2014
12:14 PM
1 Kudo
mapred.hosts still works in CDH5 It's much easier to have Cloudera Manager handle this file for you, as it will automatically be updated when adding, decommissioning, or removing hosts. Are you seeing a problem in your cluster due to this property?
... View more
08-13-2014
12:07 PM
What is your CDH version? What do the StateStore logs say? Check both the role log and the stderr. Make sure that Hive is up and healthy as well.
... View more
08-11-2014
10:56 AM
Why do you want to set this? CM manages the allowed hosts for you (using mapred.hosts).
... View more
08-01-2014
03:54 PM
Assuming you are using CM 5.0 or higher, your Cloudera Manager home page should indicate that you have stale client configuration. /etc/hadoop/conf is only updated by deploying client configuration. Until you do so, your changes won't be reflected in those files. Note that roles like NameNode and TaskTracker don't use /etc/hadoop/conf, and don't update files like /etc/hadoop/conf/core-site.xml when those roles are refreshed or restarted. Roles and commands use configuration in private subdirectories of /var/run/cloudera-scm-agent/process/ Thanks, Darren
... View more
07-31-2014
04:33 PM
Yes, you should modify the hdfs configuration for core-site.xml. Safety valves are documented here: http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM5/latest/Cloudera-Manager-Managing-Clusters/cm5mc_config_snippet.html You'll need the whole XML snippet <property>
<name>...</name>
<value>...</value>
</property> Thanks, Darren
... View more
07-31-2014
11:26 AM
3 Kudos
The fatal message is more interesting than the warning. It's complaining about incompatible cluster ids. Are you adding a datanode that already has data in the data dir on local disk? The data there probably has a conflicting cluster id. You should probably delete the local data dir(s) (or move them out of the way).
... View more
07-30-2014
12:11 PM
Did you add an Impala Service? Parcels are only for installing binaries. If you want something to actually run, you need to add and configure the appropriate service. Thanks, Darren
... View more