Member since
01-20-2014
578
Posts
102
Kudos Received
94
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
5109 | 10-28-2015 10:28 PM | |
2247 | 10-10-2015 08:30 PM | |
4205 | 10-10-2015 08:02 PM | |
3204 | 10-07-2015 02:38 PM | |
1950 | 10-06-2015 01:24 AM |
12-22-2014
01:26 PM
Let me give it a go, will provide feedback in a few hours when I get to work
... View more
12-22-2014
01:12 PM
Just to confirm, did you downloaded the .bin installer from archive.cloudera.com? Repos.jenkins is an internal host, not sure how you got that repo. Is this a new OS install? Please list the contents of your /etc/apt/sources.list and the relevant logs in /var/log/cloudera-manager-installer.
... View more
12-18-2014
04:49 PM
For a start, ensure your Cloudera Manager is also 5.2.1. We informally required that the versions be matched but it is now a requirement from 5.2 onwards. CM version should be equal or higher than CDH version. Next, go to Cloudera Management services -> even search -> critical. See if the volume related error is listed. If so, please paste details here.
... View more
12-18-2014
04:41 PM
This is a bit baffling. I created a new Trusty VM, installed CM with the .bin installer and it went through fine. I checked my apt repositories and there was no mention of Wheezy. Note that Wheezy is Debian and Trusty is Ubuntu. The .bin installer would not add the wheezy bits to /etc/apt Are you using an older machine/vm for this experiment? Can you check all files under /etc/apt to see if the wheezy repositories are present?
... View more
12-17-2014
09:28 PM
Cloudera Manager does not use any directory under /home to store anything. So I am not sure if I understand you correctly. Why do you say Cloudera Manager does not detect /dev/hda3?
... View more
12-17-2014
02:01 AM
Is this a fresh Ubuntu installation? I am not able to understand how a repo for Wheezy (Debian) was added when the OS is Trusty (Ubuntu) Are you able to track down where the wheezy repo is present and disable it? Then try again.
... View more
12-17-2014
12:25 AM
Couple of places you can check: - Host Inspector in CM - CM agent logs under /var/log/cloudera-scm-agent
... View more
12-16-2014
03:57 PM
To make things easy, you can install all the RPMs on all the nodes. Then visit CM and add the Spark service. I have been told to inform you that it is better to use Spark on YARN as of now instead of standalone Spark. This is due to performance considerations
... View more
12-16-2014
03:23 PM
That method is incorrect. The easiest way to provide a parcel to CM is to: # mkdir /opt/parcel-downloads # mv /opt/cloudera/parcels/* /opt/parcel-downloads # python -m SimpleHTTPServer 8080 Then go to CM and add http://localhost:8080 as a parcel repository. Now you can download, distribute and activate as required. After this, you can delete the contents of /opt/parcel-downloads
... View more
12-16-2014
03:13 PM
You could have mentioned the Spark requirement earlier 😉 I believe there are Spark RPMs, see here: http://archive.cloudera.com/cdh5/redhat/6/x86_64/cdh/5/RPMS/noarch/ So download the CDH5 repo # cd /etc/yum.repos.d # wget http://archive.cloudera.com/cdh5/redhat/6/x86_64/cdh/cloudera-cdh5.repo # yum makecache # yum list | grep spark
... View more